You are not logged in.
Hi
A few days ago I updated to Qt 5.15rc2 from kde-unstable repo and sddm broke.
I only saw a black screen with cursor. Today I updated to plasma 5.19 beta + Qt 5.15rc2 and got the same problem.
output of "journalctl -b" after boot with broken sddm indicates that sddm-greeter has core dumped:
-- Logs begin at Sat 2020-05-09 19:06:46 -03, end at Thu 2020-05-14 15:06:30 -03. --
mai 14 15:04:02 Arch-PC kernel: microcode: microcode updated early to revision 0x27, date = 2019-02-26
mai 14 15:04:02 Arch-PC kernel: Linux version 5.6.12-arch1-1 (linux@archlinux) (gcc version 10.1.0 (GCC)) #1 SMP PREEMPT Sun, 10 May 2020 10:43:42 +0000
mai 14 15:04:02 Arch-PC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81 rw scsi_mod.use_blk_mq=1
mai 14 15:04:02 Arch-PC kernel: KERNEL supported cpus:
mai 14 15:04:02 Arch-PC kernel: Intel GenuineIntel
mai 14 15:04:02 Arch-PC kernel: AMD AuthenticAMD
mai 14 15:04:02 Arch-PC kernel: Hygon HygonGenuine
mai 14 15:04:02 Arch-PC kernel: Centaur CentaurHauls
mai 14 15:04:02 Arch-PC kernel: zhaoxin Shanghai
mai 14 15:04:02 Arch-PC kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
mai 14 15:04:02 Arch-PC kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
mai 14 15:04:02 Arch-PC kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
mai 14 15:04:02 Arch-PC kernel: BIOS-provided physical RAM map:
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c955cfff] usable
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000c955d000-0x00000000c9563fff] ACPI NVS
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000c9564000-0x00000000c9e5dfff] usable
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000c9e5e000-0x00000000ca0c6fff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000ca0c7000-0x00000000db8b3fff] usable
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000db8b4000-0x00000000dbc21fff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000dbc22000-0x00000000dbc5cfff] usable
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000dbc5d000-0x00000000dbd1efff] ACPI NVS
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000dbd1f000-0x00000000dcffefff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000dcfff000-0x00000000dcffffff] usable
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000dd800000-0x00000000df9fffff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
mai 14 15:04:02 Arch-PC kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021e5fffff] usable
mai 14 15:04:02 Arch-PC kernel: NX (Execute Disable) protection: active
mai 14 15:04:02 Arch-PC kernel: SMBIOS 2.7 present.
mai 14 15:04:02 Arch-PC kernel: DMI: Gigabyte Technology Co., Ltd. B85M-D3PH/B85M-D3PH, BIOS F4 07/04/2014
mai 14 15:04:02 Arch-PC kernel: tsc: Fast TSC calibration using PIT
mai 14 15:04:02 Arch-PC kernel: tsc: Detected 2693.833 MHz processor
mai 14 15:04:02 Arch-PC kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
mai 14 15:04:02 Arch-PC kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
mai 14 15:04:02 Arch-PC kernel: last_pfn = 0x21e600 max_arch_pfn = 0x400000000
mai 14 15:04:02 Arch-PC kernel: MTRR default type: uncachable
mai 14 15:04:02 Arch-PC kernel: MTRR fixed ranges enabled:
mai 14 15:04:02 Arch-PC kernel: 00000-9FFFF write-back
mai 14 15:04:02 Arch-PC kernel: A0000-BFFFF uncachable
mai 14 15:04:02 Arch-PC kernel: C0000-CFFFF write-protect
mai 14 15:04:02 Arch-PC kernel: D0000-E7FFF uncachable
mai 14 15:04:02 Arch-PC kernel: E8000-FFFFF write-protect
mai 14 15:04:02 Arch-PC kernel: MTRR variable ranges enabled:
mai 14 15:04:02 Arch-PC kernel: 0 base 0000000000 mask 7E00000000 write-back
mai 14 15:04:02 Arch-PC kernel: 1 base 0200000000 mask 7FE0000000 write-back
mai 14 15:04:02 Arch-PC kernel: 2 base 00E0000000 mask 7FE0000000 uncachable
mai 14 15:04:02 Arch-PC kernel: 3 base 00DE000000 mask 7FFE000000 uncachable
mai 14 15:04:02 Arch-PC kernel: 4 base 00DD800000 mask 7FFF800000 uncachable
mai 14 15:04:02 Arch-PC kernel: 5 base 021F000000 mask 7FFF000000 uncachable
mai 14 15:04:02 Arch-PC kernel: 6 base 021E800000 mask 7FFF800000 uncachable
mai 14 15:04:02 Arch-PC kernel: 7 base 021E600000 mask 7FFFE00000 uncachable
mai 14 15:04:02 Arch-PC kernel: 8 disabled
mai 14 15:04:02 Arch-PC kernel: 9 disabled
mai 14 15:04:02 Arch-PC kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
mai 14 15:04:02 Arch-PC kernel: total RAM covered: 8126M
mai 14 15:04:02 Arch-PC kernel: Found optimal setting for mtrr clean up
mai 14 15:04:02 Arch-PC kernel: gran_size: 64K chunk_size: 64M num_reg: 10 lose cover RAM: 0G
mai 14 15:04:02 Arch-PC kernel: e820: update [mem 0xdd800000-0xffffffff] usable ==> reserved
mai 14 15:04:02 Arch-PC kernel: last_pfn = 0xdd000 max_arch_pfn = 0x400000000
mai 14 15:04:02 Arch-PC kernel: found SMP MP-table at [mem 0x000fd6d0-0x000fd6df]
mai 14 15:04:02 Arch-PC kernel: check: Scanning 1 areas for low memory corruption
mai 14 15:04:02 Arch-PC kernel: Using GB pages for direct mapping
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea401000, 0x1ea401fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea402000, 0x1ea402fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea403000, 0x1ea403fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea404000, 0x1ea404fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea405000, 0x1ea405fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea406000, 0x1ea406fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea407000, 0x1ea407fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea408000, 0x1ea408fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea409000, 0x1ea409fff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea40a000, 0x1ea40afff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea40b000, 0x1ea40bfff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: BRK [0x1ea40c000, 0x1ea40cfff] PGTABLE
mai 14 15:04:02 Arch-PC kernel: RAMDISK: [mem 0x367eb000-0x373ecfff]
mai 14 15:04:02 Arch-PC kernel: ACPI: Early table checksum verification disabled
mai 14 15:04:02 Arch-PC kernel: ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA)
mai 14 15:04:02 Arch-PC kernel: ACPI: XSDT 0x00000000DBCEB078 00006C (v01 ALASKA A M I 01072009 AMI 00010013)
mai 14 15:04:02 Arch-PC kernel: ACPI: FACP 0x00000000DBCF7E08 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
mai 14 15:04:02 Arch-PC kernel: ACPI: DSDT 0x00000000DBCEB178 00CC8D (v02 ALASKA A M I 00000088 INTL 20091112)
mai 14 15:04:02 Arch-PC kernel: ACPI: FACS 0x00000000DBD1D080 000040
mai 14 15:04:02 Arch-PC kernel: ACPI: APIC 0x00000000DBCF7F18 000062 (v03 ALASKA A M I 01072009 AMI 00010013)
mai 14 15:04:02 Arch-PC kernel: ACPI: FPDT 0x00000000DBCF7F80 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF7FC8 000539 (v01 PmRef Cpu0Ist 00003000 INTL 20120711)
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF8508 000AD8 (v01 PmRef CpuPm 00003000 INTL 20120711)
mai 14 15:04:02 Arch-PC kernel: ACPI: MCFG 0x00000000DBCF8FE0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
mai 14 15:04:02 Arch-PC kernel: ACPI: HPET 0x00000000DBCF9020 000038 (v01 ALASKA A M I 01072009 AMI. 00000005)
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF9058 00036D (v01 SataRe SataTabl 00001000 INTL 20120711)
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF93C8 0034E1 (v01 SaSsdt SaSsdt 00003000 INTL 20091112)
mai 14 15:04:02 Arch-PC kernel: ACPI: Local APIC address 0xfee00000
mai 14 15:04:02 Arch-PC kernel: No NUMA configuration found
mai 14 15:04:02 Arch-PC kernel: Faking a node at [mem 0x0000000000000000-0x000000021e5fffff]
mai 14 15:04:02 Arch-PC kernel: NODE_DATA(0) allocated [mem 0x21e5fc000-0x21e5fffff]
mai 14 15:04:02 Arch-PC kernel: Zone ranges:
mai 14 15:04:02 Arch-PC kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
mai 14 15:04:02 Arch-PC kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
mai 14 15:04:02 Arch-PC kernel: Normal [mem 0x0000000100000000-0x000000021e5fffff]
mai 14 15:04:02 Arch-PC kernel: Device empty
mai 14 15:04:02 Arch-PC kernel: Movable zone start for each node
mai 14 15:04:02 Arch-PC kernel: Early memory node ranges
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x0000000000001000-0x000000000009cfff]
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x0000000000100000-0x00000000c955cfff]
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x00000000c9564000-0x00000000c9e5dfff]
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x00000000ca0c7000-0x00000000db8b3fff]
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x00000000dbc22000-0x00000000dbc5cfff]
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x00000000dcfff000-0x00000000dcffffff]
mai 14 15:04:02 Arch-PC kernel: node 0: [mem 0x0000000100000000-0x000000021e5fffff]
mai 14 15:04:02 Arch-PC kernel: Zeroed struct page in unavailable ranges: 25572 pages
mai 14 15:04:02 Arch-PC kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000021e5fffff]
mai 14 15:04:02 Arch-PC kernel: On node 0 totalpages: 2071580
mai 14 15:04:02 Arch-PC kernel: DMA zone: 64 pages used for memmap
mai 14 15:04:02 Arch-PC kernel: DMA zone: 21 pages reserved
mai 14 15:04:02 Arch-PC kernel: DMA zone: 3996 pages, LIFO batch:0
mai 14 15:04:02 Arch-PC kernel: DMA32 zone: 13978 pages used for memmap
mai 14 15:04:02 Arch-PC kernel: DMA32 zone: 894592 pages, LIFO batch:63
mai 14 15:04:02 Arch-PC kernel: Normal zone: 18328 pages used for memmap
mai 14 15:04:02 Arch-PC kernel: Normal zone: 1172992 pages, LIFO batch:63
mai 14 15:04:02 Arch-PC kernel: Reserving Intel graphics memory at [mem 0xdda00000-0xdf9fffff]
mai 14 15:04:02 Arch-PC kernel: ACPI: PM-Timer IO Port: 0x1808
mai 14 15:04:02 Arch-PC kernel: ACPI: Local APIC address 0xfee00000
mai 14 15:04:02 Arch-PC kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
mai 14 15:04:02 Arch-PC kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
mai 14 15:04:02 Arch-PC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
mai 14 15:04:02 Arch-PC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
mai 14 15:04:02 Arch-PC kernel: ACPI: IRQ0 used by override.
mai 14 15:04:02 Arch-PC kernel: ACPI: IRQ9 used by override.
mai 14 15:04:02 Arch-PC kernel: Using ACPI (MADT) for SMP configuration information
mai 14 15:04:02 Arch-PC kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
mai 14 15:04:02 Arch-PC kernel: smpboot: Allowing 2 CPUs, 0 hotplug CPUs
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000dffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x000e0000-0x000fffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xc955d000-0xc9563fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xc9e5e000-0xca0c6fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdb8b4000-0xdbc21fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdbc5d000-0xdbd1efff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdbd1f000-0xdcffefff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdd000000-0xdd7fffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdd800000-0xdf9fffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdfa00000-0xf7ffffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
mai 14 15:04:02 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
mai 14 15:04:02 Arch-PC kernel: [mem 0xdfa00000-0xf7ffffff] available for PCI devices
mai 14 15:04:02 Arch-PC kernel: Booting paravirtualized kernel on bare hardware
mai 14 15:04:02 Arch-PC kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
mai 14 15:04:02 Arch-PC kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:2 nr_node_ids:1
mai 14 15:04:02 Arch-PC kernel: percpu: Embedded 57 pages/cpu s196608 r8192 d28672 u1048576
mai 14 15:04:02 Arch-PC kernel: pcpu-alloc: s196608 r8192 d28672 u1048576 alloc=1*2097152
mai 14 15:04:02 Arch-PC kernel: pcpu-alloc: [0] 0 1
mai 14 15:04:02 Arch-PC kernel: Built 1 zonelists, mobility grouping on. Total pages: 2039189
mai 14 15:04:02 Arch-PC kernel: Policy zone: Normal
mai 14 15:04:02 Arch-PC kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81 rw scsi_mod.use_blk_mq=1
mai 14 15:04:02 Arch-PC kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: mem auto-init: stack:byref_all, heap alloc:on, heap free:off
mai 14 15:04:02 Arch-PC kernel: Memory: 8033364K/8286320K available (12291K kernel code, 1462K rwdata, 4464K rodata, 1608K init, 3184K bss, 252956K reserved, 0K cma-reserved)
mai 14 15:04:02 Arch-PC kernel: random: get_random_u64 called from __kmem_cache_create+0x3e/0x610 with crng_init=0
mai 14 15:04:02 Arch-PC kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
mai 14 15:04:02 Arch-PC kernel: Kernel/User page tables isolation: enabled
mai 14 15:04:02 Arch-PC kernel: ftrace: allocating 39094 entries in 153 pages
mai 14 15:04:02 Arch-PC kernel: ftrace: allocated 153 pages with 4 groups
mai 14 15:04:02 Arch-PC kernel: rcu: Preemptible hierarchical RCU implementation.
mai 14 15:04:02 Arch-PC kernel: rcu: RCU dyntick-idle grace-period acceleration is enabled.
mai 14 15:04:02 Arch-PC kernel: rcu: RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=2.
mai 14 15:04:02 Arch-PC kernel: rcu: RCU priority boosting: priority 1 delay 500 ms.
mai 14 15:04:02 Arch-PC kernel: Tasks RCU enabled.
mai 14 15:04:02 Arch-PC kernel: rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.
mai 14 15:04:02 Arch-PC kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
mai 14 15:04:02 Arch-PC kernel: NR_IRQS: 20736, nr_irqs: 440, preallocated irqs: 16
mai 14 15:04:02 Arch-PC kernel: spurious 8259A interrupt: IRQ7.
mai 14 15:04:02 Arch-PC kernel: Console: colour dummy device 80x25
mai 14 15:04:02 Arch-PC kernel: printk: console [tty0] enabled
mai 14 15:04:02 Arch-PC kernel: ACPI: Core revision 20200110
mai 14 15:04:02 Arch-PC kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
mai 14 15:04:02 Arch-PC kernel: APIC: Switch to symmetric I/O mode setup
mai 14 15:04:02 Arch-PC kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
mai 14 15:04:02 Arch-PC kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x26d47cdf3d5, max_idle_ns: 440795343979 ns
mai 14 15:04:02 Arch-PC kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5389.15 BogoMIPS (lpj=8979443)
mai 14 15:04:02 Arch-PC kernel: pid_max: default: 32768 minimum: 301
mai 14 15:04:02 Arch-PC kernel: LSM: Security Framework initializing
mai 14 15:04:02 Arch-PC kernel: Yama: becoming mindful.
mai 14 15:04:02 Arch-PC kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE tmpfs ***
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE proc ***
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE cgroup ***
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE cgroup2 ***
mai 14 15:04:02 Arch-PC kernel: mce: CPU0: Thermal monitoring enabled (TM1)
mai 14 15:04:02 Arch-PC kernel: process: using mwait in idle threads
mai 14 15:04:02 Arch-PC kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
mai 14 15:04:02 Arch-PC kernel: Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
mai 14 15:04:02 Arch-PC kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
mai 14 15:04:02 Arch-PC kernel: Spectre V2 : Mitigation: Full generic retpoline
mai 14 15:04:02 Arch-PC kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
mai 14 15:04:02 Arch-PC kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
mai 14 15:04:02 Arch-PC kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
mai 14 15:04:02 Arch-PC kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
mai 14 15:04:02 Arch-PC kernel: MDS: Mitigation: Clear CPU buffers
mai 14 15:04:02 Arch-PC kernel: Freeing SMP alternatives memory: 32K
mai 14 15:04:02 Arch-PC kernel: TSC deadline timer enabled
mai 14 15:04:02 Arch-PC kernel: smpboot: CPU0: Intel(R) Celeron(R) CPU G1820 @ 2.70GHz (family: 0x6, model: 0x3c, stepping: 0x3)
mai 14 15:04:02 Arch-PC kernel: Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
mai 14 15:04:02 Arch-PC kernel: ... version: 3
mai 14 15:04:02 Arch-PC kernel: ... bit width: 48
mai 14 15:04:02 Arch-PC kernel: ... generic registers: 8
mai 14 15:04:02 Arch-PC kernel: ... value mask: 0000ffffffffffff
mai 14 15:04:02 Arch-PC kernel: ... max period: 00007fffffffffff
mai 14 15:04:02 Arch-PC kernel: ... fixed-purpose events: 3
mai 14 15:04:02 Arch-PC kernel: ... event mask: 00000007000000ff
mai 14 15:04:02 Arch-PC kernel: rcu: Hierarchical SRCU implementation.
mai 14 15:04:02 Arch-PC kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
mai 14 15:04:02 Arch-PC kernel: smp: Bringing up secondary CPUs ...
mai 14 15:04:02 Arch-PC kernel: x86: Booting SMP configuration:
mai 14 15:04:02 Arch-PC kernel: .... node #0, CPUs: #1
mai 14 15:04:02 Arch-PC kernel: smp: Brought up 1 node, 2 CPUs
mai 14 15:04:02 Arch-PC kernel: smpboot: Max logical packages: 1
mai 14 15:04:02 Arch-PC kernel: smpboot: Total of 2 processors activated (10779.30 BogoMIPS)
mai 14 15:04:02 Arch-PC kernel: devtmpfs: initialized
mai 14 15:04:02 Arch-PC kernel: x86/mm: Memory block size: 128MB
mai 14 15:04:02 Arch-PC kernel: PM: Registering ACPI NVS region [mem 0xc955d000-0xc9563fff] (28672 bytes)
mai 14 15:04:02 Arch-PC kernel: PM: Registering ACPI NVS region [mem 0xdbc5d000-0xdbd1efff] (794624 bytes)
mai 14 15:04:02 Arch-PC kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
mai 14 15:04:02 Arch-PC kernel: futex hash table entries: 512 (order: 3, 32768 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: pinctrl core: initialized pinctrl subsystem
mai 14 15:04:02 Arch-PC kernel: PM: RTC time: 18:03:54, date: 2020-05-14
mai 14 15:04:02 Arch-PC kernel: thermal_sys: Registered thermal governor 'fair_share'
mai 14 15:04:02 Arch-PC kernel: thermal_sys: Registered thermal governor 'bang_bang'
mai 14 15:04:02 Arch-PC kernel: thermal_sys: Registered thermal governor 'step_wise'
mai 14 15:04:02 Arch-PC kernel: thermal_sys: Registered thermal governor 'user_space'
mai 14 15:04:02 Arch-PC kernel: thermal_sys: Registered thermal governor 'power_allocator'
mai 14 15:04:02 Arch-PC kernel: NET: Registered protocol family 16
mai 14 15:04:02 Arch-PC kernel: audit: initializing netlink subsys (disabled)
mai 14 15:04:02 Arch-PC kernel: audit: type=2000 audit(1589479434.116:1): state=initialized audit_enabled=0 res=1
mai 14 15:04:02 Arch-PC kernel: cpuidle: using governor ladder
mai 14 15:04:02 Arch-PC kernel: cpuidle: using governor menu
mai 14 15:04:02 Arch-PC kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
mai 14 15:04:02 Arch-PC kernel: ACPI: bus type PCI registered
mai 14 15:04:02 Arch-PC kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
mai 14 15:04:02 Arch-PC kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
mai 14 15:04:02 Arch-PC kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
mai 14 15:04:02 Arch-PC kernel: PCI: Using configuration type 1 for base access
mai 14 15:04:02 Arch-PC kernel: core: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
mai 14 15:04:02 Arch-PC kernel: HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
mai 14 15:04:02 Arch-PC kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(Module Device)
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(Processor Device)
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(Processor Aggregator Device)
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(Linux-Dell-Video)
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
mai 14 15:04:02 Arch-PC kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
mai 14 15:04:02 Arch-PC kernel: ACPI: 5 ACPI AML tables successfully acquired and loaded
mai 14 15:04:02 Arch-PC kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
mai 14 15:04:02 Arch-PC kernel: ACPI: Dynamic OEM Table Load:
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0xFFFF9EC8D53D4000 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
mai 14 15:04:02 Arch-PC kernel: ACPI: Dynamic OEM Table Load:
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0xFFFF9EC8D53C7000 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
mai 14 15:04:02 Arch-PC kernel: ACPI: Dynamic OEM Table Load:
mai 14 15:04:02 Arch-PC kernel: ACPI: SSDT 0xFFFF9EC8D483D600 000119 (v01 PmRef ApCst 00003000 INTL 20120711)
mai 14 15:04:02 Arch-PC kernel: ACPI: Interpreter enabled
mai 14 15:04:02 Arch-PC kernel: ACPI: (supports S0 S3 S4 S5)
mai 14 15:04:02 Arch-PC kernel: ACPI: Using IOAPIC for interrupt routing
mai 14 15:04:02 Arch-PC kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
mai 14 15:04:02 Arch-PC kernel: ACPI: Enabled 7 GPEs in block 00 to 3F
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Resource [FN00] (off)
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Resource [FN01] (off)
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Resource [FN02] (off)
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Resource [FN03] (off)
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Resource [FN04] (off)
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
mai 14 15:04:02 Arch-PC kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
mai 14 15:04:02 Arch-PC kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug PME]
mai 14 15:04:02 Arch-PC kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability LTR]
mai 14 15:04:02 Arch-PC kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
mai 14 15:04:02 Arch-PC kernel: PCI host bridge to bus 0000:00
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0xdfa00000-0xfeafffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:00.0: [8086:0c00] type 00 class 0x060000
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: [8086:0402] type 00 class 0x030000
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7800000-0xf7bfffff 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:03.0: reg 0x10: [mem 0xf7d14000-0xf7d17fff 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7d00000-0xf7d0ffff 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7d1f000-0xf7d1f00f 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:16.3: [8086:8c3d] type 00 class 0x070002
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:16.3: reg 0x10: [io 0xf0c0-0xf0c7]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:16.3: reg 0x14: [mem 0xf7d1d000-0xf7d1dfff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7d1c000-0xf7d1c3ff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7d10000-0xf7d13fff 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.1: [8086:8c12] type 01 class 0x060400
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: [8086:8c14] type 01 class 0x060400
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7d1b000-0xf7d1b3ff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.0: [8086:8c50] type 00 class 0x060100
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: [8086:8c02] type 00 class 0x010601
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0b0-0xf0b7]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0a0-0xf0a3]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf090-0xf097]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf080-0xf083]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7d1a000-0xf7d1a7ff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.2: PME# supported from D3hot
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7d19000-0xf7d190ff 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
mai 14 15:04:02 Arch-PC kernel: pci 0000:02:00.0: [8086:244e] type 01 class 0x060401
mai 14 15:04:02 Arch-PC kernel: pci 0000:02:00.0: supports D1 D2
mai 14 15:04:02 Arch-PC kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.1: PCI bridge to [bus 02-03]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:03: extended config space not accessible
mai 14 15:04:02 Arch-PC kernel: pci 0000:02:00.0: PCI bridge to [bus 03] (subtractive decode)
mai 14 15:04:02 Arch-PC kernel: pci 0000:04:00.0: [10ec:8168] type 00 class 0x020000
mai 14 15:04:02 Arch-PC kernel: pci 0000:04:00.0: reg 0x10: [io 0xe000-0xe0ff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:04:00.0: reg 0x18: [mem 0xf7c00000-0xf7c00fff 64bit]
mai 14 15:04:02 Arch-PC kernel: pci 0000:04:00.0: reg 0x20: [mem 0xf0000000-0xf0003fff 64bit pref]
mai 14 15:04:02 Arch-PC kernel: pci 0000:04:00.0: supports D1 D2
mai 14 15:04:02 Arch-PC kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: PCI bridge to [bus 04]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: bridge window [io 0xe000-0xefff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf7c00000-0xf7cfffff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 10 11 12 14 15)
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 10 11 12 14 15)
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 10 11 12 14 15)
mai 14 15:04:02 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
mai 14 15:04:02 Arch-PC kernel: iommu: Default domain type: Translated
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: vgaarb: bridge control possible
mai 14 15:04:02 Arch-PC kernel: vgaarb: loaded
mai 14 15:04:02 Arch-PC kernel: SCSI subsystem initialized
mai 14 15:04:02 Arch-PC kernel: libata version 3.00 loaded.
mai 14 15:04:02 Arch-PC kernel: ACPI: bus type USB registered
mai 14 15:04:02 Arch-PC kernel: usbcore: registered new interface driver usbfs
mai 14 15:04:02 Arch-PC kernel: usbcore: registered new interface driver hub
mai 14 15:04:02 Arch-PC kernel: usbcore: registered new device driver usb
mai 14 15:04:02 Arch-PC kernel: pps_core: LinuxPPS API ver. 1 registered
mai 14 15:04:02 Arch-PC kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
mai 14 15:04:02 Arch-PC kernel: PTP clock support registered
mai 14 15:04:02 Arch-PC kernel: EDAC MC: Ver: 3.0.0
mai 14 15:04:02 Arch-PC kernel: PCI: Using ACPI for IRQ routing
mai 14 15:04:02 Arch-PC kernel: PCI: pci_cache_line_size set to 64 bytes
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0xc955d000-0xcbffffff]
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0xc9e5e000-0xcbffffff]
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0xdb8b4000-0xdbffffff]
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0xdbc5d000-0xdbffffff]
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0xdd000000-0xdfffffff]
mai 14 15:04:02 Arch-PC kernel: e820: reserve RAM buffer [mem 0x21e600000-0x21fffffff]
mai 14 15:04:02 Arch-PC kernel: NetLabel: Initializing
mai 14 15:04:02 Arch-PC kernel: NetLabel: domain hash size = 128
mai 14 15:04:02 Arch-PC kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
mai 14 15:04:02 Arch-PC kernel: NetLabel: unlabeled traffic allowed by default
mai 14 15:04:02 Arch-PC kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
mai 14 15:04:02 Arch-PC kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
mai 14 15:04:02 Arch-PC kernel: clocksource: Switched to clocksource tsc-early
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE bpf ***
mai 14 15:04:02 Arch-PC kernel: VFS: Disk quotas dquot_6.6.0
mai 14 15:04:02 Arch-PC kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE ramfs ***
mai 14 15:04:02 Arch-PC kernel: *** VALIDATE hugetlbfs ***
mai 14 15:04:02 Arch-PC kernel: pnp: PnP ACPI init
mai 14 15:04:02 Arch-PC kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x0680-0x069f] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0xffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0xffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0xffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x1c00-0x1cfe] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x1d00-0x1dfe] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x1e00-0x1efe] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x1f00-0x1ffe] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x1800-0x18fe] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: [io 0x164e-0x164f] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 15:04:02 Arch-PC kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
mai 14 15:04:02 Arch-PC kernel: system 00:03: [io 0x1854-0x1857] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
mai 14 15:04:02 Arch-PC kernel: system 00:04: [io 0x0a00-0x0a0f] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:04: [io 0x0a30-0x0a3f] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:04: [io 0x0a20-0x0a2f] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 15:04:02 Arch-PC kernel: system 00:05: [io 0x04d0-0x04d1] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xf7fdf000-0xf7fdffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: [mem 0xf7fe0000-0xf7feffff] has been reserved
mai 14 15:04:02 Arch-PC kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 15:04:02 Arch-PC kernel: pnp: PnP ACPI: found 7 devices
mai 14 15:04:02 Arch-PC kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
mai 14 15:04:02 Arch-PC kernel: pci 0000:02:00.0: PCI bridge to [bus 03]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.1: PCI bridge to [bus 02-03]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: PCI bridge to [bus 04]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: bridge window [io 0xe000-0xefff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf7c00000-0xf7cfffff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:00: resource 13 [mem 0xdfa00000-0xfeafffff window]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:04: resource 0 [io 0xe000-0xefff]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:04: resource 1 [mem 0xf7c00000-0xf7cfffff]
mai 14 15:04:02 Arch-PC kernel: pci_bus 0000:04: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref]
mai 14 15:04:02 Arch-PC kernel: NET: Registered protocol family 2
mai 14 15:04:02 Arch-PC kernel: tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: TCP: Hash tables configured (established 65536 bind 65536)
mai 14 15:04:02 Arch-PC kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
mai 14 15:04:02 Arch-PC kernel: NET: Registered protocol family 1
mai 14 15:04:02 Arch-PC kernel: NET: Registered protocol family 44
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x6d5 took 20037 usecs
mai 14 15:04:02 Arch-PC kernel: pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x6d5 took 19511 usecs
mai 14 15:04:02 Arch-PC kernel: PCI: CLS 64 bytes, default 64
mai 14 15:04:02 Arch-PC kernel: Trying to unpack rootfs image as initramfs...
mai 14 15:04:02 Arch-PC kernel: Freeing initrd memory: 12296K
mai 14 15:04:02 Arch-PC kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
mai 14 15:04:02 Arch-PC kernel: software IO TLB: mapped [mem 0xd78b4000-0xdb8b4000] (64MB)
mai 14 15:04:02 Arch-PC kernel: check: Scanning for low memory corruption every 60 seconds
mai 14 15:04:02 Arch-PC kernel: Initialise system trusted keyrings
mai 14 15:04:02 Arch-PC kernel: Key type blacklist registered
mai 14 15:04:02 Arch-PC kernel: workingset: timestamp_bits=41 max_order=21 bucket_order=0
mai 14 15:04:02 Arch-PC kernel: zbud: loaded
mai 14 15:04:02 Arch-PC kernel: Key type asymmetric registered
mai 14 15:04:02 Arch-PC kernel: Asymmetric key parser 'x509' registered
mai 14 15:04:02 Arch-PC kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
mai 14 15:04:02 Arch-PC kernel: io scheduler mq-deadline registered
mai 14 15:04:02 Arch-PC kernel: io scheduler kyber registered
mai 14 15:04:02 Arch-PC kernel: io scheduler bfq registered
mai 14 15:04:02 Arch-PC kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
mai 14 15:04:02 Arch-PC kernel: vesafb: mode is 1920x1080x32, linelength=7680, pages=0
mai 14 15:04:02 Arch-PC kernel: vesafb: scrolling: redraw
mai 14 15:04:02 Arch-PC kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
mai 14 15:04:02 Arch-PC kernel: vesafb: framebuffer at 0xe0000000, mapped to 0x00000000962056a3, using 8128k, total 8128k
mai 14 15:04:02 Arch-PC kernel: fbcon: Deferring console take-over
mai 14 15:04:02 Arch-PC kernel: fb0: VESA VGA frame buffer device
mai 14 15:04:02 Arch-PC kernel: intel_idle: MWAIT substates: 0x2120
mai 14 15:04:02 Arch-PC kernel: intel_idle: v0.4.1 model 0x3C
mai 14 15:04:02 Arch-PC kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
mai 14 15:04:02 Arch-PC kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Button [PWRB]
mai 14 15:04:02 Arch-PC kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
mai 14 15:04:02 Arch-PC kernel: ACPI: Power Button [PWRF]
mai 14 15:04:02 Arch-PC kernel: thermal LNXTHERM:00: registered as thermal_zone0
mai 14 15:04:02 Arch-PC kernel: ACPI: Thermal Zone [TZ00] (28 C)
mai 14 15:04:02 Arch-PC kernel: thermal LNXTHERM:01: registered as thermal_zone1
mai 14 15:04:02 Arch-PC kernel: ACPI: Thermal Zone [TZ01] (30 C)
mai 14 15:04:02 Arch-PC kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
mai 14 15:04:02 Arch-PC kernel: 0000:00:16.3: ttyS0 at I/O 0xf0c0 (irq = 19, base_baud = 115200) is a 16550A
mai 14 15:04:02 Arch-PC kernel: AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
mai 14 15:04:02 Arch-PC kernel: AMD-Vi: AMD IOMMUv2 functionality not available on this system
mai 14 15:04:02 Arch-PC kernel: ahci 0000:00:1f.2: version 3.0
mai 14 15:04:02 Arch-PC kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1b impl SATA mode
mai 14 15:04:02 Arch-PC kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst
mai 14 15:04:02 Arch-PC kernel: scsi host0: ahci
mai 14 15:04:02 Arch-PC kernel: scsi host1: ahci
mai 14 15:04:02 Arch-PC kernel: scsi host2: ahci
mai 14 15:04:02 Arch-PC kernel: scsi host3: ahci
mai 14 15:04:02 Arch-PC kernel: scsi host4: ahci
mai 14 15:04:02 Arch-PC kernel: scsi host5: ahci
mai 14 15:04:02 Arch-PC kernel: ata1: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a100 irq 27
mai 14 15:04:02 Arch-PC kernel: ata2: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a180 irq 27
mai 14 15:04:02 Arch-PC kernel: ata3: DUMMY
mai 14 15:04:02 Arch-PC kernel: ata4: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a280 irq 27
mai 14 15:04:02 Arch-PC kernel: ata5: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a300 irq 27
mai 14 15:04:02 Arch-PC kernel: ata6: DUMMY
mai 14 15:04:02 Arch-PC kernel: usbcore: registered new interface driver usbserial_generic
mai 14 15:04:02 Arch-PC kernel: usbserial: USB Serial support registered for generic
mai 14 15:04:02 Arch-PC kernel: rtc_cmos 00:02: RTC can wake from S4
mai 14 15:04:02 Arch-PC kernel: rtc_cmos 00:02: registered as rtc0
mai 14 15:04:02 Arch-PC kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
mai 14 15:04:02 Arch-PC kernel: intel_pstate: Intel P-state driver initializing
mai 14 15:04:02 Arch-PC kernel: ledtrig-cpu: registered to indicate activity on CPUs
mai 14 15:04:02 Arch-PC kernel: drop_monitor: Initializing network drop monitor service
mai 14 15:04:02 Arch-PC kernel: NET: Registered protocol family 10
mai 14 15:04:02 Arch-PC kernel: Segment Routing with IPv6
mai 14 15:04:02 Arch-PC kernel: NET: Registered protocol family 17
mai 14 15:04:02 Arch-PC kernel: RAS: Correctable Errors collector initialized.
mai 14 15:04:02 Arch-PC kernel: microcode: sig=0x306c3, pf=0x2, revision=0x27
mai 14 15:04:02 Arch-PC kernel: microcode: Microcode Update Driver: v2.2.
mai 14 15:04:02 Arch-PC kernel: IPI shorthand broadcast: enabled
mai 14 15:04:02 Arch-PC kernel: sched_clock: Marking stable (514129170, 195823)->(519045274, -4720281)
mai 14 15:04:02 Arch-PC kernel: registered taskstats version 1
mai 14 15:04:02 Arch-PC kernel: Loading compiled-in X.509 certificates
mai 14 15:04:02 Arch-PC kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 8efc0745a0f4f1a15f5910b82807b1e1a48255ac'
mai 14 15:04:02 Arch-PC kernel: zswap: loaded using pool lzo/zbud
mai 14 15:04:02 Arch-PC kernel: Key type ._fscrypt registered
mai 14 15:04:02 Arch-PC kernel: Key type .fscrypt registered
mai 14 15:04:02 Arch-PC kernel: Key type fscrypt-provisioning registered
mai 14 15:04:02 Arch-PC kernel: Key type big_key registered
mai 14 15:04:02 Arch-PC kernel: PM: Magic number: 4:468:89
mai 14 15:04:02 Arch-PC kernel: rtc_cmos 00:02: setting system clock to 2020-05-14T18:03:55 UTC (1589479435)
mai 14 15:04:02 Arch-PC kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
mai 14 15:04:02 Arch-PC kernel: ata1.00: HPA detected: current 1953523055, native 1953525168
mai 14 15:04:02 Arch-PC kernel: ata1.00: ATA-9: WDC WD10EZEX-00BN5A0, 01.01A01, max UDMA/133
mai 14 15:04:02 Arch-PC kernel: ata1.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 32), AA
mai 14 15:04:02 Arch-PC kernel: ata1.00: configured for UDMA/133
mai 14 15:04:02 Arch-PC kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD10EZEX-00B 1A01 PQ: 0 ANSI: 5
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: [sda] 1953523055 512-byte logical blocks: (1.00 TB/932 GiB)
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: [sda] Write Protect is off
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mai 14 15:04:02 Arch-PC kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
mai 14 15:04:02 Arch-PC kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
mai 14 15:04:02 Arch-PC kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
mai 14 15:04:02 Arch-PC kernel: ata4.00: ATA-9: ST2000DM006-2DM164, CC26, max UDMA/133
mai 14 15:04:02 Arch-PC kernel: ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
mai 14 15:04:02 Arch-PC kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
mai 14 15:04:02 Arch-PC kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
mai 14 15:04:02 Arch-PC kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
mai 14 15:04:02 Arch-PC kernel: ata2.00: HPA detected: current 1953523055, native 1953525168
mai 14 15:04:02 Arch-PC kernel: ata2.00: ATA-8: ST31000524AS, JC45, max UDMA/133
mai 14 15:04:02 Arch-PC kernel: ata2.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 32)
mai 14 15:04:02 Arch-PC kernel: ata5.00: ATAPI: HL-DT-ST BD-RE WH14NS40, 1.03, max UDMA/100
mai 14 15:04:02 Arch-PC kernel: ata4.00: configured for UDMA/133
mai 14 15:04:02 Arch-PC kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
mai 14 15:04:02 Arch-PC kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
mai 14 15:04:02 Arch-PC kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
mai 14 15:04:02 Arch-PC kernel: ata2.00: configured for UDMA/133
mai 14 15:04:02 Arch-PC kernel: scsi 1:0:0:0: Direct-Access ATA ST31000524AS JC45 PQ: 0 ANSI: 5
mai 14 15:04:02 Arch-PC kernel: ata5.00: configured for UDMA/100
mai 14 15:04:02 Arch-PC kernel: sd 1:0:0:0: [sdb] 1953523055 512-byte logical blocks: (1.00 TB/932 GiB)
mai 14 15:04:02 Arch-PC kernel: sd 1:0:0:0: [sdb] Write Protect is off
mai 14 15:04:02 Arch-PC kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
mai 14 15:04:02 Arch-PC kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mai 14 15:04:02 Arch-PC kernel: scsi 3:0:0:0: Direct-Access ATA ST2000DM006-2DM1 CC26 PQ: 0 ANSI: 5
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: [sdc] 4096-byte physical blocks
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: [sdc] Write Protect is off
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mai 14 15:04:02 Arch-PC kernel: scsi 4:0:0:0: CD-ROM HL-DT-ST BD-RE WH14NS40 1.03 PQ: 0 ANSI: 5
mai 14 15:04:02 Arch-PC kernel: sdb: sdb1
mai 14 15:04:02 Arch-PC kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
mai 14 15:04:02 Arch-PC kernel: sda: sda1 sda2 sda3 sda4
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: [sda] Attached SCSI disk
mai 14 15:04:02 Arch-PC kernel: sdc: sdc1
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
mai 14 15:04:02 Arch-PC kernel: Freeing unused decrypted memory: 2040K
mai 14 15:04:02 Arch-PC kernel: Freeing unused kernel image (initmem) memory: 1608K
mai 14 15:04:02 Arch-PC kernel: Write protecting the kernel read-only data: 20480k
mai 14 15:04:02 Arch-PC kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
mai 14 15:04:02 Arch-PC kernel: Freeing unused kernel image (rodata/data gap) memory: 1680K
mai 14 15:04:02 Arch-PC kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
mai 14 15:04:02 Arch-PC kernel: x86/mm: Checking user space page tables
mai 14 15:04:02 Arch-PC kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
mai 14 15:04:02 Arch-PC kernel: Run /init as init process
mai 14 15:04:02 Arch-PC kernel: with arguments:
mai 14 15:04:02 Arch-PC kernel: /init
mai 14 15:04:02 Arch-PC kernel: with environment:
mai 14 15:04:02 Arch-PC kernel: HOME=/
mai 14 15:04:02 Arch-PC kernel: TERM=linux
mai 14 15:04:02 Arch-PC kernel: BOOT_IMAGE=/boot/vmlinuz-linux
mai 14 15:04:02 Arch-PC kernel: fbcon: Taking over console
mai 14 15:04:02 Arch-PC kernel: Console: switching to colour frame buffer device 240x67
mai 14 15:04:02 Arch-PC kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mai 14 15:04:02 Arch-PC kernel: ehci-pci: EHCI PCI platform driver
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1a.0: debug port 2
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7d1c000
mai 14 15:04:02 Arch-PC kernel: sr 4:0:0:0: [sr0] scsi3-mmc drive: 47x/94x writer dvd-ram cd/rw xa/form2 cdda tray
mai 14 15:04:02 Arch-PC kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
mai 14 15:04:02 Arch-PC kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
mai 14 15:04:02 Arch-PC kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 15:04:02 Arch-PC kernel: usb usb1: Product: EHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: usb usb1: Manufacturer: Linux 5.6.12-arch1-1 ehci_hcd
mai 14 15:04:02 Arch-PC kernel: usb usb1: SerialNumber: 0000:00:1a.0
mai 14 15:04:02 Arch-PC kernel: hub 1-0:1.0: USB hub found
mai 14 15:04:02 Arch-PC kernel: hub 1-0:1.0: 2 ports detected
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
mai 14 15:04:02 Arch-PC kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
mai 14 15:04:02 Arch-PC kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 15:04:02 Arch-PC kernel: usb usb2: Product: xHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: usb usb2: Manufacturer: Linux 5.6.12-arch1-1 xhci-hcd
mai 14 15:04:02 Arch-PC kernel: usb usb2: SerialNumber: 0000:00:14.0
mai 14 15:04:02 Arch-PC kernel: hub 2-0:1.0: USB hub found
mai 14 15:04:02 Arch-PC kernel: hub 2-0:1.0: 12 ports detected
mai 14 15:04:02 Arch-PC kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
mai 14 15:04:02 Arch-PC kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.06
mai 14 15:04:02 Arch-PC kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 15:04:02 Arch-PC kernel: usb usb3: Product: xHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: usb usb3: Manufacturer: Linux 5.6.12-arch1-1 xhci-hcd
mai 14 15:04:02 Arch-PC kernel: usb usb3: SerialNumber: 0000:00:14.0
mai 14 15:04:02 Arch-PC kernel: hub 3-0:1.0: USB hub found
mai 14 15:04:02 Arch-PC kernel: hub 3-0:1.0: 6 ports detected
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1d.0: debug port 2
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7d1b000
mai 14 15:04:02 Arch-PC kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
mai 14 15:04:02 Arch-PC kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
mai 14 15:04:02 Arch-PC kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 15:04:02 Arch-PC kernel: usb usb4: Product: EHCI Host Controller
mai 14 15:04:02 Arch-PC kernel: usb usb4: Manufacturer: Linux 5.6.12-arch1-1 ehci_hcd
mai 14 15:04:02 Arch-PC kernel: usb usb4: SerialNumber: 0000:00:1d.0
mai 14 15:04:02 Arch-PC kernel: hub 4-0:1.0: USB hub found
mai 14 15:04:02 Arch-PC kernel: hub 4-0:1.0: 2 ports detected
mai 14 15:04:02 Arch-PC kernel: random: fast init done
mai 14 15:04:02 Arch-PC kernel: tsc: Refined TSC clocksource calibration: 2693.761 MHz
mai 14 15:04:02 Arch-PC kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x26d438c619d, max_idle_ns: 440795237946 ns
mai 14 15:04:02 Arch-PC kernel: clocksource: Switched to clocksource tsc
mai 14 15:04:02 Arch-PC kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
mai 14 15:04:02 Arch-PC kernel: usb 2-9: new low-speed USB device number 2 using xhci_hcd
mai 14 15:04:02 Arch-PC kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
mai 14 15:04:02 Arch-PC kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=8008, bcdDevice= 0.05
mai 14 15:04:02 Arch-PC kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
mai 14 15:04:02 Arch-PC kernel: hub 1-1:1.0: USB hub found
mai 14 15:04:02 Arch-PC kernel: hub 1-1:1.0: 6 ports detected
mai 14 15:04:02 Arch-PC kernel: usb 2-9: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=64.00
mai 14 15:04:02 Arch-PC kernel: usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
mai 14 15:04:02 Arch-PC kernel: usb 2-9: Product: USB Keyboard
mai 14 15:04:02 Arch-PC kernel: usb 2-9: Manufacturer: Logitech
mai 14 15:04:02 Arch-PC kernel: hid: raw HID events driver (C) Jiri Kosina
mai 14 15:04:02 Arch-PC kernel: usbcore: registered new interface driver usbhid
mai 14 15:04:02 Arch-PC kernel: usbhid: USB HID core driver
mai 14 15:04:02 Arch-PC kernel: input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/0003:046D:C31C.0001/input/input2
mai 14 15:04:02 Arch-PC kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.05
mai 14 15:04:02 Arch-PC kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
mai 14 15:04:02 Arch-PC kernel: hub 4-1:1.0: USB hub found
mai 14 15:04:02 Arch-PC kernel: hub 4-1:1.0: 6 ports detected
mai 14 15:04:02 Arch-PC kernel: hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-0000:00:14.0-9/input0
mai 14 15:04:02 Arch-PC kernel: input: Logitech USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/input/input3
mai 14 15:04:02 Arch-PC kernel: usb 2-10: new low-speed USB device number 3 using xhci_hcd
mai 14 15:04:02 Arch-PC kernel: input: Logitech USB Keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/input/input4
mai 14 15:04:02 Arch-PC kernel: hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-0000:00:14.0-9/input1
mai 14 15:04:02 Arch-PC kernel: usb 2-10: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00
mai 14 15:04:02 Arch-PC kernel: usb 2-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
mai 14 15:04:02 Arch-PC kernel: usb 2-10: Product: USB Optical Mouse
mai 14 15:04:02 Arch-PC kernel: usb 2-10: Manufacturer: Logitech
mai 14 15:04:02 Arch-PC kernel: input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/0003:046D:C077.0003/input/input5
mai 14 15:04:02 Arch-PC kernel: hid-generic 0003:046D:C077.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-10/input0
mai 14 15:04:02 Arch-PC kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
mai 14 15:04:02 Arch-PC kernel: random: crng init done
mai 14 15:04:02 Arch-PC systemd[1]: systemd 245.5-2-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
mai 14 15:04:02 Arch-PC systemd[1]: Detected architecture x86-64.
mai 14 15:04:02 Arch-PC systemd[1]: Set hostname to <Arch-PC>.
mai 14 15:04:02 Arch-PC systemd[1]: Created slice system-getty.slice.
mai 14 15:04:02 Arch-PC systemd[1]: Created slice system-modprobe.slice.
mai 14 15:04:02 Arch-PC systemd[1]: Created slice User and Session Slice.
mai 14 15:04:02 Arch-PC systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
mai 14 15:04:02 Arch-PC systemd[1]: Started Forward Password Requests to Wall Directory Watch.
mai 14 15:04:02 Arch-PC systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
mai 14 15:04:02 Arch-PC systemd[1]: Reached target Local Encrypted Volumes.
mai 14 15:04:02 Arch-PC systemd[1]: Reached target Login Prompts.
mai 14 15:04:02 Arch-PC systemd[1]: Reached target Paths.
mai 14 15:04:02 Arch-PC systemd[1]: Reached target Remote File Systems.
mai 14 15:04:02 Arch-PC systemd[1]: Reached target Slices.
mai 14 15:04:02 Arch-PC systemd[1]: Reached target Swap.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on Device-mapper event daemon FIFOs.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on LVM2 metadata daemon socket.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on LVM2 poll daemon socket.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on Process Core Dump Socket.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on initctl Compatibility Named Pipe.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on Journal Audit Socket.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on Journal Socket (/dev/log).
mai 14 15:04:02 Arch-PC systemd[1]: Listening on Journal Socket.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on udev Control Socket.
mai 14 15:04:02 Arch-PC systemd[1]: Listening on udev Kernel Socket.
mai 14 15:04:02 Arch-PC systemd[1]: Mounting Huge Pages File System...
mai 14 15:04:02 Arch-PC systemd[1]: Mounting POSIX Message Queue File System...
mai 14 15:04:02 Arch-PC systemd[1]: Mounting Kernel Debug File System...
mai 14 15:04:02 Arch-PC systemd[1]: Mounting Kernel Trace File System...
mai 14 15:04:02 Arch-PC systemd[1]: Mounting Temporary Directory (/tmp)...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Create list of static device nodes for the current kernel...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Load Kernel Module drm...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Set Up Additional Binary Formats...
mai 14 15:04:02 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:04:02 Arch-PC systemd[1]: Starting Journal Service...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Load Kernel Modules...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Remount Root and Kernel File Systems...
mai 14 15:04:02 Arch-PC systemd[1]: Starting udev Coldplug all Devices...
mai 14 15:04:02 Arch-PC systemd[1]: Mounted Huge Pages File System.
mai 14 15:04:02 Arch-PC systemd[1]: Mounted POSIX Message Queue File System.
mai 14 15:04:02 Arch-PC systemd[1]: Mounted Kernel Debug File System.
mai 14 15:04:02 Arch-PC systemd[1]: Mounted Kernel Trace File System.
mai 14 15:04:02 Arch-PC systemd[1]: Mounted Temporary Directory (/tmp).
mai 14 15:04:02 Arch-PC systemd[1]: Finished Create list of static device nodes for the current kernel.
mai 14 15:04:02 Arch-PC kernel: Linux agpgart interface v0.103
mai 14 15:04:02 Arch-PC systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 270 (systemd-binfmt)
mai 14 15:04:02 Arch-PC systemd[1]: Mounting Arbitrary Executable File Formats File System...
mai 14 15:04:02 Arch-PC systemd[1]: Mounted Arbitrary Executable File Formats File System.
mai 14 15:04:02 Arch-PC kernel: EXT4-fs (sda3): re-mounted. Opts: (null)
mai 14 15:04:02 Arch-PC systemd[1]: Finished Remount Root and Kernel File Systems.
mai 14 15:04:02 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:04:02 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:04:02 Arch-PC systemd[1]: Starting Load/Save Random Seed...
mai 14 15:04:02 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:04:02 Arch-PC systemd[1]: Starting Create Static Device Nodes in /dev...
mai 14 15:04:02 Arch-PC systemd[1]: modprobe@drm.service: Succeeded.
mai 14 15:04:02 Arch-PC systemd[1]: Finished Load Kernel Module drm.
mai 14 15:04:02 Arch-PC systemd[1]: Finished Set Up Additional Binary Formats.
mai 14 15:04:02 Arch-PC systemd[1]: Started LVM2 metadata daemon.
mai 14 15:04:02 Arch-PC systemd[1]: Finished udev Coldplug all Devices.
mai 14 15:04:02 Arch-PC kernel: vhba: loading out-of-tree module taints kernel.
mai 14 15:04:02 Arch-PC kernel: vhba: module verification failed: signature and/or required key missing - tainting kernel
mai 14 15:04:02 Arch-PC kernel: scsi host6: vhba
mai 14 15:04:02 Arch-PC systemd[1]: Finished Load/Save Random Seed.
mai 14 15:04:02 Arch-PC kernel: audit: type=1130 audit(1589479442.145:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC systemd-journald[271]: Journal started
mai 14 15:04:02 Arch-PC systemd-journald[271]: Runtime Journal (/run/log/journal/4bac3062eca442b1b88ff64657a50777) is 8.0M, max 393.2M, 385.2M free.
mai 14 15:04:02 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC systemd-modules-load[272]: Inserted module 'crypto_user'
mai 14 15:04:02 Arch-PC systemd-modules-load[272]: Inserted module 'vhba'
mai 14 15:04:02 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC systemd[1]: Starting Flush Journal to Persistent Storage...
mai 14 15:04:02 Arch-PC systemd[1]: Started Journal Service.
mai 14 15:04:02 Arch-PC kernel: audit: type=1130 audit(1589479442.172:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC systemd-modules-load[272]: Inserted module 'sg'
mai 14 15:04:02 Arch-PC kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
mai 14 15:04:02 Arch-PC kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
mai 14 15:04:02 Arch-PC kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0
mai 14 15:04:02 Arch-PC kernel: sr 4:0:0:0: Attached scsi generic sg3 type 5
mai 14 15:04:02 Arch-PC systemd-journald[271]: Time spent on flushing to /var/log/journal/4bac3062eca442b1b88ff64657a50777 is 730.456ms for 789 entries.
mai 14 15:04:02 Arch-PC systemd-journald[271]: System Journal (/var/log/journal/4bac3062eca442b1b88ff64657a50777) is 4.0G, max 4.0G, 0B free.
mai 14 15:04:05 Arch-PC kernel: vboxdrv: Found 2 processor cores
mai 14 15:04:05 Arch-PC kernel: vboxdrv: TSC mode is Invariant, tentative frequency 2693758316 Hz
mai 14 15:04:05 Arch-PC kernel: vboxdrv: Successfully loaded version 6.1.6 (interface 0x002d0001)
mai 14 15:04:05 Arch-PC kernel: VBoxNetAdp: Successfully started.
mai 14 15:04:05 Arch-PC kernel: VBoxNetFlt: Successfully started.
mai 14 15:04:05 Arch-PC kernel: audit: type=1130 audit(1589479442.375:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:05 Arch-PC kernel: audit: type=1130 audit(1589479442.669:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:05 Arch-PC kernel: audit: type=1130 audit(1589479442.892:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:05 Arch-PC kernel: audit: type=1334 audit(1589479442.895:7): prog-id=5 op=LOAD
mai 14 15:04:05 Arch-PC kernel: audit: type=1334 audit(1589479442.895:8): prog-id=6 op=LOAD
mai 14 15:04:02 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:05 Arch-PC kernel: audit: type=1130 audit(1589479445.435:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC audit: AUDIT1334 prog-id=5 op=LOAD
mai 14 15:04:02 Arch-PC audit: AUDIT1334 prog-id=6 op=LOAD
mai 14 15:04:05 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:02 Arch-PC systemd-modules-load[272]: Inserted module 'vboxdrv'
mai 14 15:04:02 Arch-PC systemd-modules-load[272]: Inserted module 'vboxnetadp'
mai 14 15:04:02 Arch-PC systemd-modules-load[272]: Inserted module 'vboxnetflt'
mai 14 15:04:02 Arch-PC systemd[1]: Finished Load Kernel Modules.
mai 14 15:04:02 Arch-PC systemd[1]: Condition check resulted in FUSE Control File System being skipped.
mai 14 15:04:02 Arch-PC systemd[1]: Mounting Kernel Configuration File System...
mai 14 15:04:02 Arch-PC systemd[1]: Starting Apply Kernel Variables...
mai 14 15:04:02 Arch-PC systemd[1]: Mounted Kernel Configuration File System.
mai 14 15:04:02 Arch-PC systemd-sysctl[289]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
mai 14 15:04:02 Arch-PC systemd-sysctl[289]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
mai 14 15:04:02 Arch-PC systemd-sysctl[289]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
mai 14 15:04:02 Arch-PC systemd-sysctl[289]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists).
mai 14 15:04:02 Arch-PC systemd-sysctl[289]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
mai 14 15:04:02 Arch-PC systemd-sysctl[289]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
mai 14 15:04:02 Arch-PC systemd[1]: Finished Apply Kernel Variables.
mai 14 15:04:02 Arch-PC systemd[1]: Finished Create Static Device Nodes in /dev.
mai 14 15:04:02 Arch-PC systemd[1]: Starting udev Kernel Device Manager...
mai 14 15:04:05 Arch-PC systemd[1]: Finished Flush Journal to Persistent Storage.
mai 14 15:04:05 Arch-PC systemd[1]: Started udev Kernel Device Manager.
mai 14 15:04:05 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:05 Arch-PC kernel: audit: type=1130 audit(1589479445.842:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:06 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20200110/utaddress-204)
mai 14 15:04:06 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 15:04:06 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200110/utaddress-204)
mai 14 15:04:06 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 15:04:06 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200110/utaddress-204)
mai 14 15:04:06 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200110/utaddress-204)
mai 14 15:04:06 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 15:04:06 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200110/utaddress-204)
mai 14 15:04:06 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200110/utaddress-204)
mai 14 15:04:06 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 15:04:06 Arch-PC kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
mai 14 15:04:06 Arch-PC kernel: i801_smbus 0000:00:1f.3: enabling device (0001 -> 0003)
mai 14 15:04:06 Arch-PC kernel: i801_smbus 0000:00:1f.3: SPD Write Disable is set
mai 14 15:04:06 Arch-PC kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
mai 14 15:04:06 Arch-PC kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
mai 14 15:04:06 Arch-PC systemd-udevd[305]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
mai 14 15:04:06 Arch-PC kernel: r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
mai 14 15:04:06 Arch-PC kernel: RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
mai 14 15:04:06 Arch-PC kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
mai 14 15:04:06 Arch-PC kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
mai 14 15:04:06 Arch-PC kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
mai 14 15:04:06 Arch-PC kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
mai 14 15:04:06 Arch-PC kernel: libphy: r8169: probed
mai 14 15:04:06 Arch-PC kernel: r8169 0000:04:00.0 eth0: RTL8168evl/8111evl, fc:aa:14:fc:4b:1b, XID 2c9, IRQ 30
mai 14 15:04:06 Arch-PC kernel: r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
mai 14 15:04:06 Arch-PC mtp-probe[335]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-9"
mai 14 15:04:06 Arch-PC systemd-udevd[292]: Using default interface naming scheme 'v245'.
mai 14 15:04:06 Arch-PC mtp-probe[335]: bus: 2, device: 2 was not an MTP device
mai 14 15:04:06 Arch-PC mtp-probe[334]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-10"
mai 14 15:04:06 Arch-PC mtp-probe[334]: bus: 2, device: 3 was not an MTP device
mai 14 15:04:06 Arch-PC systemd-udevd[292]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
mai 14 15:04:06 Arch-PC kernel: r8169 0000:04:00.0 enp4s0: renamed from eth0
mai 14 15:04:06 Arch-PC systemd[1]: Found device ST31000524AS SEAGATE.
mai 14 15:04:06 Arch-PC systemd-udevd[308]: Using default interface naming scheme 'v245'.
mai 14 15:04:06 Arch-PC systemd[1]: Found device ST2000DM006-2DM164 2TB.
mai 14 15:04:06 Arch-PC kernel: iTCO_vendor_support: vendor-support=0
mai 14 15:04:06 Arch-PC kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
mai 14 15:04:06 Arch-PC kernel: iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: mono: mono_out=0x0
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: dig-out=0x11/0x0
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: inputs:
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: Rear Mic=0x18
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: Front Mic=0x19
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: Line=0x1a
mai 14 15:04:06 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: CD=0x1c
mai 14 15:04:06 Arch-PC kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card1/input7
mai 14 15:04:06 Arch-PC kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input8
mai 14 15:04:06 Arch-PC kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9
mai 14 15:04:06 Arch-PC kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card1/input10
mai 14 15:04:06 Arch-PC kernel: input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card1/input11
mai 14 15:04:06 Arch-PC kernel: intel-spi intel-spi: mx25l6405d (8192 Kbytes)
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in FUSE Control File System being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:04:07 Arch-PC kernel: checking generic (e0000000 7f0000) vs hw (f7800000 400000)
mai 14 15:04:07 Arch-PC kernel: checking generic (e0000000 7f0000) vs hw (e0000000 10000000)
mai 14 15:04:07 Arch-PC kernel: fb0: switching to inteldrmfb from VESA VGA
mai 14 15:04:07 Arch-PC kernel: Console: switching to colour dummy device 80x25
mai 14 15:04:07 Arch-PC kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
mai 14 15:04:07 Arch-PC kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
mai 14 15:04:07 Arch-PC kernel: [drm] Driver supports precise vblank timestamp query.
mai 14 15:04:07 Arch-PC kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
mai 14 15:04:07 Arch-PC kernel: [drm] Initialized i915 1.6.0 20200114 for 0000:00:02.0 on minor 0
mai 14 15:04:07 Arch-PC kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
mai 14 15:04:07 Arch-PC kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
mai 14 15:04:07 Arch-PC kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
mai 14 15:04:07 Arch-PC kernel: Creating 1 MTD partitions on "intel-spi":
mai 14 15:04:07 Arch-PC kernel: 0x000000000000-0x000000800000 : "BIOS"
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:04:07 Arch-PC kernel: fbcon: i915drmfb (fb0) is primary device
mai 14 15:04:07 Arch-PC kernel: Console: switching to colour frame buffer device 240x67
mai 14 15:04:07 Arch-PC kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in FUSE Control File System being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:04:07 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:04:07 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input13
mai 14 15:04:07 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input14
mai 14 15:04:07 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input15
mai 14 15:04:07 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/sound/card0/input16
mai 14 15:04:07 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.0/sound/card0/input17
mai 14 15:04:07 Arch-PC kernel: mousedev: PS/2 mouse device common for all mice
mai 14 15:04:07 Arch-PC kernel: cryptd: max_cpu_qlen set to 1000
mai 14 15:04:08 Arch-PC systemd-udevd[298]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
mai 14 15:04:08 Arch-PC systemd-udevd[301]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
mai 14 15:04:08 Arch-PC systemd[1]: Found device WDC_WD10EZEX-00BN5A0 WD.
mai 14 15:04:08 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:08 Arch-PC systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
mai 14 15:04:08 Arch-PC kernel: audit: type=1130 audit(1589479448.635:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:08 Arch-PC kernel: intel_rapl_common: Found RAPL domain package
mai 14 15:04:08 Arch-PC kernel: intel_rapl_common: Found RAPL domain core
mai 14 15:04:08 Arch-PC kernel: intel_rapl_common: Found RAPL domain uncore
mai 14 15:04:08 Arch-PC kernel: intel_rapl_common: Found RAPL domain dram
mai 14 15:04:08 Arch-PC systemd[1]: Reached target Local File Systems (Pre).
mai 14 15:04:08 Arch-PC systemd[1]: Mounting /mnt/2TB...
mai 14 15:04:09 Arch-PC kernel: fuse: init (API version 7.31)
mai 14 15:04:09 Arch-PC kernel: *** VALIDATE fuseblk ***
mai 14 15:04:09 Arch-PC kernel: *** VALIDATE fuse ***
mai 14 15:04:09 Arch-PC kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
mai 14 15:04:08 Arch-PC systemd[1]: Mounting /mnt/SEAGATE...
mai 14 15:04:08 Arch-PC systemd[1]: mnt-WD.mount: Directory /mnt/WD to mount over is not empty, mounting anyway.
mai 14 15:04:08 Arch-PC systemd[1]: Mounting /mnt/WD...
mai 14 15:04:08 Arch-PC systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for b1freearchiver...
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for b1freearchiver...
mai 14 15:04:09 Arch-PC ntfs-3g[452]: Version 2017.3.23 external FUSE 29
mai 14 15:04:09 Arch-PC ntfs-3g[452]: Mounted /dev/sdc1 (Read-Write, label "2TB", NTFS 3.1)
mai 14 15:04:09 Arch-PC ntfs-3g[452]: Cmdline options: rw,nosuid,nodev
mai 14 15:04:09 Arch-PC ntfs-3g[452]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,fsname=/dev/sdc1,blkdev,blksize=4096
mai 14 15:04:09 Arch-PC ntfs-3g[452]: Ownership and permissions disabled, configuration type 7
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for boa, revision 196...
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for boa, revision 202...
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for core, revision 8935...
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for core, revision 9066...
mai 14 15:04:09 Arch-PC kernel: loop: module loaded
mai 14 15:04:09 Arch-PC systemd[1]: Mounting Mount unit for core18, revision 1705...
mai 14 15:04:09 Arch-PC ntfs-3g[468]: Version 2017.3.23 external FUSE 29
mai 14 15:04:09 Arch-PC ntfs-3g[468]: Mounted /dev/sdb1 (Read-Write, label "SEAGATE", NTFS 3.1)
mai 14 15:04:09 Arch-PC ntfs-3g[468]: Cmdline options: rw,nosuid,nodev
mai 14 15:04:09 Arch-PC ntfs-3g[468]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096
mai 14 15:04:09 Arch-PC ntfs-3g[468]: Ownership and permissions disabled, configuration type 7
mai 14 15:04:10 Arch-PC kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
mai 14 15:04:10 Arch-PC systemd[1]: Mounting Mount unit for core18, revision 1754...
mai 14 15:04:10 Arch-PC systemd[1]: Mounting Mount unit for gnome-3-26-1604, revision 97...
mai 14 15:04:10 Arch-PC systemd[1]: Mounting Mount unit for gnome-3-26-1604, revision 98...
mai 14 15:04:10 Arch-PC systemd[1]: Mounting Mount unit for gnome-3-28-1804, revision 116...
mai 14 15:04:11 Arch-PC systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1502...
mai 14 15:04:11 Arch-PC systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1506...
mai 14 15:04:11 Arch-PC systemd[1]: Mounting Mount unit for kde-frameworks-5, revision 27...
mai 14 15:04:11 Arch-PC systemd[1]: Mounting Mount unit for opendvdproducer, revision 60...
mai 14 15:04:11 Arch-PC systemd[1]: Mounted /mnt/2TB.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted /mnt/SEAGATE.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted /mnt/WD.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for b1freearchiver.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for b1freearchiver.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for boa, revision 196.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for boa, revision 202.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for core, revision 8935.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for core, revision 9066.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for core18, revision 1705.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for core18, revision 1754.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for gnome-3-26-1604, revision 97.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for gnome-3-26-1604, revision 98.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for gnome-3-28-1804, revision 116.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1502.
mai 14 15:04:11 Arch-PC systemd[1]: Mounting FUSE Control File System...
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1506.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted FUSE Control File System.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for kde-frameworks-5, revision 27.
mai 14 15:04:11 Arch-PC systemd[1]: Mounted Mount unit for opendvdproducer, revision 60.
mai 14 15:04:11 Arch-PC systemd[1]: Reached target Local File Systems.
mai 14 15:04:11 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 15:04:11 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 15:04:11 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 15:04:11 Arch-PC systemd[1]: Starting Create Volatile Files and Directories...
mai 14 15:04:12 Arch-PC systemd[1]: Finished Create Volatile Files and Directories.
mai 14 15:04:12 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 15:04:12 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 15:04:12 Arch-PC kernel: audit: type=1130 audit(1589479452.362:12): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC systemd[1]: Starting Update UTMP about System Boot/Shutdown...
mai 14 15:04:12 Arch-PC audit[492]: SYSTEM_BOOT pid=492 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC kernel: audit: type=1127 audit(1589479452.405:13): pid=492 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC systemd[1]: Finished Update UTMP about System Boot/Shutdown.
mai 14 15:04:12 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC systemd[1]: Reached target System Initialization.
mai 14 15:04:12 Arch-PC kernel: audit: type=1130 audit(1589479452.439:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC systemd[1]: Started Daily atop restart.
mai 14 15:04:12 Arch-PC systemd[1]: Started Daily rotation of log files.
mai 14 15:04:12 Arch-PC systemd[1]: Started Daily man-db regeneration.
mai 14 15:04:12 Arch-PC systemd[1]: Started Monthly clean packages cache.
mai 14 15:04:12 Arch-PC systemd[1]: Started Daily verification of password and group files.
mai 14 15:04:12 Arch-PC systemd[1]: Started Daily Cleanup of Temporary Directories.
mai 14 15:04:12 Arch-PC systemd[1]: Reached target Timers.
mai 14 15:04:12 Arch-PC systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
mai 14 15:04:12 Arch-PC systemd[1]: Listening on D-Bus System Message Bus Socket.
mai 14 15:04:12 Arch-PC systemd[1]: Starting Socket activation for snappy daemon.
mai 14 15:04:12 Arch-PC systemd[1]: Listening on Socket activation for snappy daemon.
mai 14 15:04:12 Arch-PC systemd[1]: Reached target Sockets.
mai 14 15:04:12 Arch-PC systemd[1]: Reached target Basic System.
mai 14 15:04:12 Arch-PC systemd[1]: Condition check resulted in Save/Restore Sound Card State being skipped.
mai 14 15:04:12 Arch-PC systemd[1]: Condition check resulted in Manage Sound Card State (restore and store) being skipped.
mai 14 15:04:12 Arch-PC systemd[1]: Reached target Sound Card.
mai 14 15:04:12 Arch-PC systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
mai 14 15:04:12 Arch-PC kernel: audit: type=1130 audit(1589479452.512:15): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:12 Arch-PC avahi-daemon[494]: Found user 'avahi' (UID 978) and group 'avahi' (GID 978).
mai 14 15:04:12 Arch-PC systemd[1]: Starting CDEmu Daemon...
mai 14 15:04:12 Arch-PC systemd[1]: Started D-Bus System Message Bus.
mai 14 15:04:12 Arch-PC systemd[1]: Starting Network Manager...
mai 14 15:04:12 Arch-PC systemd[1]: Starting Initialize hardware monitoring sensors...
mai 14 15:04:12 Arch-PC systemd[1]: Condition check resulted in SSH Key Generation being skipped.
mai 14 15:04:12 Arch-PC audit: AUDIT1334 prog-id=7 op=LOAD
mai 14 15:04:12 Arch-PC kernel: audit: type=1334 audit(1589479452.912:16): prog-id=7 op=LOAD
mai 14 15:04:12 Arch-PC kernel: audit: type=1334 audit(1589479452.912:17): prog-id=8 op=LOAD
mai 14 15:04:12 Arch-PC audit: AUDIT1334 prog-id=8 op=LOAD
mai 14 15:04:12 Arch-PC kernel: it87: Found IT8620E chip at 0xa30, revision 4
mai 14 15:04:12 Arch-PC kernel: it87: Beeping is supported
mai 14 15:04:12 Arch-PC systemd[1]: Starting Login Service...
mai 14 15:04:12 Arch-PC avahi-daemon[494]: Successfully dropped root privileges.
mai 14 15:04:12 Arch-PC avahi-daemon[494]: avahi-daemon 0.8 starting up.
mai 14 15:04:13 Arch-PC systemd[1]: Finished Initialize hardware monitoring sensors.
mai 14 15:04:13 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lm_sensors comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:13 Arch-PC kernel: audit: type=1130 audit(1589479453.175:18): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lm_sensors comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:13 Arch-PC systemd-logind[499]: New seat seat0.
mai 14 15:04:14 Arch-PC kernel: audit: type=1130 audit(1589479454.335:19): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC kernel: audit: type=1130 audit(1589479454.335:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC kernel: audit: type=1130 audit(1589479454.339:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:13 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event1 (Power Button)
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Successfully called chroot().
mai 14 15:04:13 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event0 (Power Button)
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Successfully dropped remaining capabilities.
mai 14 15:04:13 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event2 (Logitech USB Keyboard)
mai 14 15:04:14 Arch-PC avahi-daemon[494]: No service file found in /etc/avahi/services.
mai 14 15:04:13 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event4 (Logitech USB Keyboard System Control)
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
mai 14 15:04:13 Arch-PC NetworkManager[497]: <info> [1589479453.9508] NetworkManager (version 1.24.0-1) is starting... (for the first time)
mai 14 15:04:14 Arch-PC kernel: audit: type=1130 audit(1589479454.512:22): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emby-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC kernel: audit: type=1130 audit(1589479454.519:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=limbomedia comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: audit: type=1130 audit(1589479454.522:24): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: scsi 6:0:1:0: CD-ROM CDEmu CD-ROM 1.0 PQ: 0 ANSI: 0
mai 14 15:04:30 Arch-PC kernel: sr 6:0:1:0: [sr1] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
mai 14 15:04:30 Arch-PC kernel: sr 6:0:1:0: Attached scsi CD-ROM sr1
mai 14 15:04:30 Arch-PC kernel: sr 6:0:1:0: Attached scsi generic sg4 type 5
mai 14 15:04:30 Arch-PC kernel: audit: type=1130 audit(1589479460.752:25): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: audit: type=1130 audit(1589479460.755:26): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cdemu-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: audit: type=1130 audit(1589479460.762:27): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: audit: type=1334 audit(1589479460.762:28): prog-id=9 op=LOAD
mai 14 15:04:30 Arch-PC kernel: audit: type=1334 audit(1589479460.762:29): prog-id=10 op=LOAD
mai 14 15:04:30 Arch-PC kernel: audit: type=1130 audit(1589479461.472:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: audit: type=1130 audit(1589479461.615:31): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=subsonic comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:30 Arch-PC kernel: RTL8211E Gigabit Ethernet r8169-400:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
mai 14 15:04:30 Arch-PC kernel: r8169 0000:04:00.0 enp4s0: Link is Down
mai 14 15:04:30 Arch-PC kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
mai 14 15:04:30 Arch-PC kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
mai 14 15:04:30 Arch-PC kernel: audit: type=1334 audit(1589479465.149:32): prog-id=11 op=LOAD
mai 14 15:04:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emby-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=limbomedia comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:20 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:20 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cdemu-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:20 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:20 Arch-PC audit: AUDIT1334 prog-id=9 op=LOAD
mai 14 15:04:20 Arch-PC audit: AUDIT1334 prog-id=10 op=LOAD
mai 14 15:04:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:31 Arch-PC kernel: audit: type=1130 audit(1589479470.679:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:31 Arch-PC kernel: audit: type=1130 audit(1589479471.532:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=subsonic comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:25 Arch-PC audit: AUDIT1334 prog-id=11 op=LOAD
mai 14 15:04:30 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:31 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC avahi-daemon[494]: New relevant interface lo.IPv6 for mDNS.
mai 14 15:04:13 Arch-PC NetworkManager[497]: <info> [1589479453.9617] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
mai 14 15:04:14 Arch-PC systemd[1]: Started Login Service.
mai 14 15:04:14 Arch-PC avahi-daemon[494]: New relevant interface lo.IPv4 for mDNS.
mai 14 15:04:31 Arch-PC emby-server[509]: Info Main: Application path: /usr/lib/emby-server/EmbyServer.dll
mai 14 15:04:31 Arch-PC emby-server[509]: Info Main: Emby
mai 14 15:04:31 Arch-PC emby-server[509]: Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /var/lib/emby -ffdetect /usr/bin/ffdetect-emby -ffmpeg /usr/bin/ffmpeg-emby -ffprobe /usr/bin/ffprobe-emby -restartexitcode 3
mai 14 15:04:31 Arch-PC emby-server[509]: Operating system: Unix 5.6.12.1
mai 14 15:04:31 Arch-PC emby-server[509]: 64-Bit OS: True
mai 14 15:04:31 Arch-PC emby-server[509]: 64-Bit Process: True
mai 14 15:04:31 Arch-PC emby-server[509]: User Interactive: True
mai 14 15:04:31 Arch-PC emby-server[509]: Runtime: file:///usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Private.CoreLib.dll
mai 14 15:04:31 Arch-PC emby-server[509]: System.Environment.Version: 3.1.3
mai 14 15:04:31 Arch-PC emby-server[509]: Processor count: 2
mai 14 15:04:31 Arch-PC emby-server[509]: Program data path: /var/lib/emby
mai 14 15:04:31 Arch-PC emby-server[509]: Application directory: /usr/lib/emby-server
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: Application version: 4.4.2.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: Loading assemblies
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/Fanart.dll has version 1.0.7.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/Fanart.dll has version 1.0.7.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/StudioImages.dll has version 1.0.3.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/StudioImages.dll has version 1.0.3.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/DvdMounter.dll has version 1.0.0.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/DvdMounter.dll has version 1.0.0.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/OpenSubtitles.dll has version 1.0.26.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/OpenSubtitles.dll has version 1.0.26.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/Emby.PortMapper.dll has version 1.0.4.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/Emby.PortMapper.dll has version 1.0.4.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/Emby.Server.CinemaMode.dll has version 1.0.31.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/Emby.Server.CinemaMode.dll has version 1.0.31.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/NfoMetadata.dll has version 1.0.29.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/NfoMetadata.dll has version 1.0.29.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/Emby.Webhooks.dll has version 1.0.11.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/Emby.Webhooks.dll has version 1.0.11.0
mai 14 15:04:31 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/Emby.Dlna.dll has version 1.0.37.0
mai 14 15:04:35 Arch-PC kernel: audit: type=1100 audit(1589479474.039:35): pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
mai 14 15:04:35 Arch-PC kernel: audit: type=1101 audit(1589479474.039:36): pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
mai 14 15:04:35 Arch-PC kernel: audit: type=1103 audit(1589479474.079:37): pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
mai 14 15:04:34 Arch-PC audit[597]: USER_AUTH pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
mai 14 15:04:34 Arch-PC audit[597]: USER_ACCT pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
mai 14 15:04:34 Arch-PC audit[597]: CRED_ACQ pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
mai 14 15:04:14 Arch-PC systemd[1]: Started Avahi mDNS/DNS-SD Stack.
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Network interface enumeration completed.
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/Emby.Dlna.dll has version 1.0.37.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/Tvdb.dll has version 1.0.31.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/Tvdb.dll has version 1.0.30.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/BlurayMounter.dll has version 1.0.0.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/BlurayMounter.dll has version 1.0.0.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/MovieDb.dll has version 1.3.4.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/MovieDb.dll has version 1.3.1.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/AudioDb.dll has version 1.0.10.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/AudioDb.dll has version 1.0.9.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/MusicBrainz.dll has version 1.0.13.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/MusicBrainz.dll has version 1.0.13.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /var/lib/emby/plugins/OMDb.dll has version 1.0.9.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: File /usr/lib/emby-server/plugins/OMDb.dll has version 1.0.9.0
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Fanart, Version=1.0.7.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Fanart.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/StudioImages.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading DvdMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/DvdMounter.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading OpenSubtitles, Version=1.0.26.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OpenSubtitles.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.PortMapper, Version=1.0.4.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.PortMapper.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Server.CinemaMode, Version=1.0.31.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Server.CinemaMode.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading NfoMetadata, Version=1.0.29.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/NfoMetadata.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Webhooks, Version=1.0.11.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Webhooks.dll
mai 14 15:04:14 Arch-PC NetworkManager[497]: <info> [1589479454.3406] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Registering new address record for ::1 on lo.*.
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Dlna, Version=1.0.37.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Dlna.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Tvdb, Version=1.0.31.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Tvdb.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading BlurayMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/BlurayMounter.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading MovieDb, Version=1.3.4.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MovieDb.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading AudioDb, Version=1.0.10.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/AudioDb.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading MusicBrainz, Version=1.0.13.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MusicBrainz.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading OMDb, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OMDb.dll
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Api, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Web, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading MediaBrowser.Model, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading MediaBrowser.Common, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading MediaBrowser.Controller, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Providers, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Photos, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Server.Implementations, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.LiveTV, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.ActivityLog, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Server.MediaEncoding, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.LocalMetadata, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Notifications, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:14 Arch-PC systemd[1]: Started Network Manager.
mai 14 15:04:14 Arch-PC avahi-daemon[494]: Registering new address record for 127.0.0.1 on lo.IPv4.
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Codecs.Dxva, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Codecs, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Server.Connect, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading Emby.Server.Sync, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:35 Arch-PC emby-server[509]: Info App: Loading EmbyServer, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 15:04:14 Arch-PC systemd[1]: Reached target Network.
mai 14 15:04:14 Arch-PC dbus-daemon[496]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.3' (uid=0 pid=497 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 15:04:35 Arch-PC subsonic.sh[512]: Started Subsonic [PID 557, /var/lib/subsonic/subsonic_sh.log]
mai 14 15:04:14 Arch-PC systemd[1]: Starting Network Manager Wait Online...
mai 14 15:04:15 Arch-PC avahi-daemon[494]: Server startup complete. Host name is Arch-PC.local. Local service cookie is 1579200519.
mai 14 15:04:14 Arch-PC NetworkManager[497]: <info> [1589479454.4022] manager[0x56045c85d080]: monitoring kernel firmware directory '/lib/firmware'.
mai 14 15:04:15 Arch-PC sshd[511]: Server listening on 0.0.0.0 port 22.
mai 14 15:04:14 Arch-PC systemd[1]: Started Emby brings together your videos, music, photos, and live television..
mai 14 15:04:15 Arch-PC sshd[511]: Server listening on :: port 22.
mai 14 15:04:14 Arch-PC systemd[1]: Started LimboMedia.
mai 14 15:04:21 Arch-PC dbus-daemon[496]: [system] Successfully activated service 'org.freedesktop.hostname1'
mai 14 15:04:14 Arch-PC systemd[1]: Started OpenSSH Daemon.
mai 14 15:04:21 Arch-PC dbus-daemon[496]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=497 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 15:04:14 Arch-PC systemd[1]: Starting Subsonic...
mai 14 15:04:25 Arch-PC avahi-daemon[494]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.50.
mai 14 15:04:14 Arch-PC systemd[1]: Starting Permit User Sessions...
mai 14 15:04:25 Arch-PC avahi-daemon[494]: New relevant interface enp4s0.IPv4 for mDNS.
mai 14 15:04:20 Arch-PC systemd[1]: Finished Permit User Sessions.
mai 14 15:04:25 Arch-PC avahi-daemon[494]: Registering new address record for 192.168.0.50 on enp4s0.IPv4.
mai 14 15:04:20 Arch-PC systemd[1]: Started CDEmu Daemon.
mai 14 15:04:26 Arch-PC avahi-daemon[494]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::feaa:14ff:fefc:4b1b.
mai 14 15:04:20 Arch-PC systemd[1]: Started Simple Desktop Display Manager.
mai 14 15:04:26 Arch-PC avahi-daemon[494]: New relevant interface enp4s0.IPv6 for mDNS.
mai 14 15:04:20 Arch-PC systemd[1]: Starting Hostname Service...
mai 14 15:04:26 Arch-PC avahi-daemon[494]: Registering new address record for fe80::feaa:14ff:fefc:4b1b on enp4s0.*.
mai 14 15:04:21 Arch-PC systemd[1]: Started Hostname Service.
mai 14 15:04:27 Arch-PC dbus-daemon[496]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.3' (uid=0 pid=497 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.4927] hostname: hostname: using hostnamed
mai 14 15:04:30 Arch-PC dbus-daemon[496]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.4927] hostname: hostname changed from (none) to "Arch-PC"
mai 14 15:04:30 Arch-PC dbus-daemon[496]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.5286] dns-mgr[0x56045c839220]: init: dns=default,systemd-resolved rc-manager=symlink
mai 14 15:04:30 Arch-PC dbus-daemon[496]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.3' (uid=0 pid=497 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 15:04:21 Arch-PC systemd[1]: Started Subsonic.
mai 14 15:04:30 Arch-PC dbus-daemon[496]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.6372] manager[0x56045c85d080]: rfkill: Wi-Fi hardware radio set disabled
mai 14 15:04:34 Arch-PC sddm-helper[597]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.6372] manager[0x56045c85d080]: rfkill: WWAN hardware radio set disabled
mai 14 15:04:34 Arch-PC nmbd[596]: [2020/05/14 15:04:34.545009, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.7188] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-ovs.so)
mai 14 15:04:34 Arch-PC nmbd[596]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.7662] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-wwan.so)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8258] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-team.so)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8337] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-wifi.so)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8386] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-adsl.so)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8697] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-bluetooth.so)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8704] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8706] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8707] manager: Networking is enabled by state file
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8850] dhcp-init: Using DHCP client 'internal'
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.8944] settings: Loaded settings plugin: keyfile (internal)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.9411] device (lo): carrier: link connected
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.9417] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.9447] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
mai 14 15:04:21 Arch-PC NetworkManager[497]: <info> [1589479461.9460] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
mai 14 15:04:22 Arch-PC NetworkManager[497]: <info> [1589479462.2060] ovsdb: Não foi possível conectar: Arquivo ou diretório inexistente
mai 14 15:04:25 Arch-PC sddm[551]: Initializing...
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1179] device (enp4s0): carrier: link connected
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1187] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1420] policy: auto-activating connection 'Internet' (ce90ca86-a34c-30a3-a2e6-db85b51a19a9)
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1443] device (enp4s0): Activation: starting connection 'Internet' (ce90ca86-a34c-30a3-a2e6-db85b51a19a9)
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1451] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1481] manager: NetworkManager state is now CONNECTING
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1496] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1513] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mai 14 15:04:25 Arch-PC NetworkManager[497]: <info> [1589479465.1546] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
mai 14 15:04:25 Arch-PC sddm[551]: Starting...
mai 14 15:04:25 Arch-PC sddm[551]: Logind interface found
mai 14 15:04:25 Arch-PC sddm[551]: Adding new display on vt 1 ...
mai 14 15:04:25 Arch-PC sddm[551]: Loading theme configuration from ""
mai 14 15:04:25 Arch-PC sddm[551]: Display server starting...
mai 14 15:04:25 Arch-PC sddm[551]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{640f92fc-dc58-4577-8393-13f89f132d66} -background none -noreset -displayfd 17 -seat seat0 vt1
mai 14 15:04:30 Arch-PC sddm[551]: Setting default cursor
mai 14 15:04:30 Arch-PC systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
mai 14 15:04:30 Arch-PC systemd[1]: Starting Network Manager Script Dispatcher Service...
mai 14 15:04:30 Arch-PC systemd[1]: Started Network Manager Script Dispatcher Service.
mai 14 15:04:30 Arch-PC NetworkManager[497]: <info> [1589479470.8862] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
mai 14 15:04:30 Arch-PC NetworkManager[497]: <info> [1589479470.8875] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
mai 14 15:04:36 Arch-PC kernel: audit: type=1130 audit(1589479476.052:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nmb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC kernel: audit: type=1130 audit(1589479476.242:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC kernel: audit: type=1101 audit(1589479476.562:40): pid=607 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC kernel: audit: type=1103 audit(1589479476.562:41): pid=607 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 15:04:36 Arch-PC kernel: audit: type=1006 audit(1589479476.562:42): pid=607 uid=0 old-auid=4294967295 auid=977 tty=(none) old-ses=4294967295 ses=1 res=1
mai 14 15:04:36 Arch-PC kernel: audit: type=1105 audit(1589479476.655:43): pid=607 uid=0 auid=977 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC kernel: audit: type=1334 audit(1589479476.679:44): prog-id=12 op=LOAD
mai 14 15:04:36 Arch-PC kernel: audit: type=1334 audit(1589479476.679:45): prog-id=12 op=UNLOAD
mai 14 15:04:36 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nmb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC audit[607]: USER_ACCT pid=607 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC audit[607]: CRED_ACQ pid=607 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 15:04:36 Arch-PC audit[607]: USER_START pid=607 uid=0 auid=977 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:36 Arch-PC audit: AUDIT1334 prog-id=12 op=LOAD
mai 14 15:04:36 Arch-PC audit: AUDIT1334 prog-id=12 op=UNLOAD
mai 14 15:04:30 Arch-PC NetworkManager[497]: <info> [1589479470.8883] manager: NetworkManager state is now CONNECTED_LOCAL
mai 14 15:04:36 Arch-PC systemd[607]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
mai 14 15:04:37 Arch-PC emby-server[509]: Info SqliteUserRepository: Sqlite version: 3.31.1
mai 14 15:04:37 Arch-PC emby-server[509]: Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-9.2.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_JSON1,ENABLE_RTREE,ENABLE_UNLOCK_NOTIFY,HAVE_ISNAN,MAX_EXPR_DEPTH=10000,MAX_VARIABLE_NUMBER=250000,SECURE_DELETE,TEMP_STORE=1,THREADSAFE=1
mai 14 15:04:30 Arch-PC NetworkManager[497]: <info> [1589479470.8896] manager: NetworkManager state is now CONNECTED_SITE
mai 14 15:04:36 Arch-PC systemd[607]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
mai 14 15:04:30 Arch-PC NetworkManager[497]: <info> [1589479470.8900] policy: set 'Internet' (enp4s0) as default for IPv4 routing and DNS
mai 14 15:04:30 Arch-PC sddm[551]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
mai 14 15:04:31 Arch-PC NetworkManager[497]: <info> [1589479471.4044] device (enp4s0): Activation: successful, device activated.
mai 14 15:04:31 Arch-PC NetworkManager[497]: <info> [1589479471.4057] manager: startup complete
mai 14 15:04:31 Arch-PC systemd[1]: Finished Network Manager Wait Online.
mai 14 15:04:31 Arch-PC systemd[1]: Reached target Network is Online.
mai 14 15:04:31 Arch-PC sddm[551]: Display server started.
mai 14 15:04:31 Arch-PC sddm[551]: Socket server starting...
mai 14 15:04:31 Arch-PC sddm[551]: Socket server started.
mai 14 15:04:31 Arch-PC systemd[1]: Starting Samba NMB Daemon...
mai 14 15:04:31 Arch-PC NetworkManager[497]: <info> [1589479471.6502] manager: NetworkManager state is now CONNECTED_GLOBAL
mai 14 15:04:32 Arch-PC sddm[551]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
mai 14 15:04:32 Arch-PC sddm[551]: Greeter starting...
mai 14 15:04:32 Arch-PC sddm[551]: Adding cookie to "/var/run/sddm/{640f92fc-dc58-4577-8393-13f89f132d66}"
mai 14 15:04:34 Arch-PC sddm-helper[597]: [PAM] Starting...
mai 14 15:04:34 Arch-PC sddm-helper[597]: [PAM] Authenticating...
mai 14 15:04:34 Arch-PC sddm-helper[597]: [PAM] returning.
mai 14 15:04:36 Arch-PC systemd[1]: Started Samba NMB Daemon.
mai 14 15:04:36 Arch-PC systemd[1]: Created slice User Slice of UID 977.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Starting Samba SMB Daemon...
mai 14 15:04:36 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/977...
mai 14 15:04:36 Arch-PC systemd-logind[499]: New session c1 of user sddm.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 15:04:36 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/977.
mai 14 15:04:36 Arch-PC systemd[1]: Starting User Manager for UID 977...
mai 14 15:04:38 Arch-PC systemd[607]: Reached target Paths.
mai 14 15:04:38 Arch-PC systemd[607]: Reached target Timers.
mai 14 15:04:38 Arch-PC systemd[607]: Starting D-Bus User Message Bus Socket.
mai 14 15:04:38 Arch-PC systemd[607]: Listening on GnuPG network certificate management daemon.
mai 14 15:04:38 Arch-PC systemd[607]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 15:04:38 Arch-PC systemd[607]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 15:04:38 Arch-PC systemd[607]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 15:04:38 Arch-PC systemd[607]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 15:04:38 Arch-PC systemd[607]: Listening on p11-kit server.
mai 14 15:04:38 Arch-PC systemd[607]: Listening on Multimedia System.
mai 14 15:04:38 Arch-PC systemd[607]: Listening on Sound System.
mai 14 15:04:38 Arch-PC systemd[607]: Listening on D-Bus User Message Bus Socket.
mai 14 15:04:38 Arch-PC systemd[607]: Reached target Sockets.
mai 14 15:04:38 Arch-PC systemd[607]: Reached target Basic System.
mai 14 15:04:38 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:38 Arch-PC systemd[1]: Started User Manager for UID 977.
mai 14 15:04:38 Arch-PC systemd[1]: Started Session c1 of user sddm.
mai 14 15:04:38 Arch-PC kernel: audit: type=1130 audit(1589479478.195:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:38 Arch-PC kernel: audit: type=1105 audit(1589479478.202:47): pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
mai 14 15:04:38 Arch-PC audit[597]: USER_START pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
mai 14 15:04:38 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:38 Arch-PC smbd[605]: [2020/05/14 15:04:38.821243, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
mai 14 15:04:38 Arch-PC systemd[607]: Starting Update XDG user dir configuration...
mai 14 15:04:38 Arch-PC smbd[605]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
mai 14 15:04:38 Arch-PC sddm[551]: Greeter session started successfully
mai 14 15:04:38 Arch-PC systemd[607]: xdg-user-dirs-update.service: Succeeded.
mai 14 15:04:38 Arch-PC systemd[607]: Finished Update XDG user dir configuration.
mai 14 15:04:38 Arch-PC systemd[607]: Reached target Main User Target.
mai 14 15:04:38 Arch-PC systemd[607]: Startup finished in 1.729s.
mai 14 15:04:38 Arch-PC sddm-greeter[624]: High-DPI autoscaling not Enabled
mai 14 15:04:38 Arch-PC systemd[1]: Started Samba SMB Daemon.
mai 14 15:04:38 Arch-PC systemd[1]: Reached target Multi-User System.
mai 14 15:04:38 Arch-PC systemd[1]: Reached target Graphical Interface.
mai 14 15:04:38 Arch-PC systemd[1]: Startup finished in 2.907s (kernel) + 40.945s (userspace) = 43.852s.
mai 14 15:04:39 Arch-PC sddm-greeter[624]: Could not load the Qt platform plugin "xcb" in "" even though it was found.
mai 14 15:04:39 Arch-PC audit[624]: ANOM_ABEND auid=4294967295 uid=977 gid=977 ses=4294967295 pid=624 comm="sddm-greeter" exe="/usr/bin/sddm-greeter" sig=6 res=1
mai 14 15:04:39 Arch-PC sddm-greeter[624]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
mai 14 15:04:39 Arch-PC java[510]: 2020-05-14 15:04:39,910 INFO lm.system - Starting LimboMedia Server ...
mai 14 15:04:40 Arch-PC audit: AUDIT1334 prog-id=13 op=LOAD
mai 14 15:04:40 Arch-PC audit: AUDIT1334 prog-id=14 op=LOAD
mai 14 15:04:40 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-629-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:40 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:41 Arch-PC emby-server[509]: Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is wal
mai 14 15:04:41 Arch-PC java[510]: 2020-05-14 15:04:39,972 INFO lm.system - Execution location: /home/stalker/limbomedia
mai 14 15:04:41 Arch-PC java[510]: 2020-05-14 15:04:39,972 INFO lm.system - Datastore location: /home/stalker/limbomedia/data
mai 14 15:04:41 Arch-PC java[510]: 2020-05-14 15:04:39,973 INFO lm.system - Server config file: /home/stalker/limbomedia/data/limbomedia.cfg
mai 14 15:04:41 Arch-PC java[510]: 2020-05-14 15:04:39,978 INFO lm.system - Environment: Linux, 5.6.12-arch1-1, amd64 - Java 1.8.0_242, Oracle Corporation
mai 14 15:04:41 Arch-PC java[510]: 2020-05-14 15:04:40,109 INFO lm.system - Environment: Charset UTF-8, File Encoding UTF-8, Timezone America/Sao_Paulo - Fuso horário de Brasília
mai 14 15:04:41 Arch-PC java[510]: 2020-05-14 15:04:40,671 INFO lm.system - Starting module core -> The heart and soul of LimboMedia.
mai 14 15:04:40 Arch-PC systemd[1]: Created slice system-systemd\x2dcoredump.slice.
mai 14 15:04:40 Arch-PC systemd[1]: Started Process Core Dump (PID 629/UID 0).
mai 14 15:04:40 Arch-PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mai 14 15:04:41 Arch-PC emby-server[509]: Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is wal
mai 14 15:04:41 Arch-PC emby-server[509]: Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is wal
mai 14 15:04:41 Arch-PC emby-server[509]: Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is wal
mai 14 15:04:41 Arch-PC emby-server[509]: Info App: Adding HttpListener prefix http://+:8096/
mai 14 15:04:41 Arch-PC sddm-helper[597]: [PAM] Closing session
mai 14 15:04:41 Arch-PC sddm-helper[597]: pam_unix(sddm-greeter:session): session closed for user sddm
mai 14 15:04:41 Arch-PC audit[597]: USER_END pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
mai 14 15:04:41 Arch-PC audit[597]: CRED_DISP pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
mai 14 15:04:41 Arch-PC sddm-helper[597]: [PAM] Ended.
mai 14 15:04:41 Arch-PC kernel: kauditd_printk_skb: 6 callbacks suppressed
mai 14 15:04:41 Arch-PC kernel: audit: type=1106 audit(1589479481.892:54): pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
mai 14 15:04:41 Arch-PC kernel: audit: type=1104 audit(1589479481.892:55): pid=597 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
mai 14 15:04:42 Arch-PC systemd[1]: session-c1.scope: Succeeded.
mai 14 15:04:42 Arch-PC systemd-logind[499]: Session c1 logged out. Waiting for processes to exit.
mai 14 15:04:42 Arch-PC sddm[551]: Auth: sddm-helper exited with 6
mai 14 15:04:42 Arch-PC sddm[551]: Greeter stopped.
mai 14 15:04:42 Arch-PC systemd-logind[499]: Removed session c1.
mai 14 15:04:42 Arch-PC systemd-coredump[637]: Process 624 (sddm-greeter) of user 977 dumped core.
Stack trace of thread 624:
#0 0x00007fd7390e42e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007fd7390cd853 abort (libc.so.6 + 0x25853)
#2 0x00007fd7394f69ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007fd739aea0e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007fd739aea581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007fd73971f2e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007fd739aed5c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007fd739aee528 _ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x137528)
#8 0x000055f889ce693b main (sddm-greeter + 0x1993b)
#9 0x00007fd7390cf002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x000055f889ce6f3e _start (sddm-greeter + 0x19f3e)
mai 14 15:04:42 Arch-PC systemd[1]: systemd-coredump@0-629-0.service: Succeeded.
mai 14 15:04:42 Arch-PC kernel: audit: type=1131 audit(1589479482.399:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-629-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:42 Arch-PC kernel: audit: type=1334 audit(1589479482.452:57): prog-id=14 op=UNLOAD
mai 14 15:04:42 Arch-PC kernel: audit: type=1334 audit(1589479482.452:58): prog-id=13 op=UNLOAD
mai 14 15:04:42 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-629-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:42 Arch-PC audit: AUDIT1334 prog-id=14 op=UNLOAD
mai 14 15:04:42 Arch-PC audit: AUDIT1334 prog-id=13 op=UNLOAD
mai 14 15:04:44 Arch-PC emby-server[509]: Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is wal
mai 14 15:04:51 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:51 Arch-PC systemd[1]: systemd-hostnamed.service: Succeeded.
mai 14 15:04:51 Arch-PC kernel: audit: type=1131 audit(1589479491.519:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:51 Arch-PC audit: AUDIT1334 prog-id=10 op=UNLOAD
mai 14 15:04:51 Arch-PC audit: AUDIT1334 prog-id=9 op=UNLOAD
mai 14 15:04:51 Arch-PC kernel: audit: type=1334 audit(1589479491.565:60): prog-id=10 op=UNLOAD
mai 14 15:04:51 Arch-PC kernel: audit: type=1334 audit(1589479491.565:61): prog-id=9 op=UNLOAD
mai 14 15:04:52 Arch-PC systemd[1]: Stopping User Manager for UID 977...
mai 14 15:04:52 Arch-PC systemd[607]: Stopped target Main User Target.
mai 14 15:04:52 Arch-PC systemd[607]: Stopped target Basic System.
mai 14 15:04:52 Arch-PC systemd[607]: Stopped target Paths.
mai 14 15:04:52 Arch-PC systemd[607]: Stopped target Sockets.
mai 14 15:04:52 Arch-PC systemd[607]: Stopped target Timers.
mai 14 15:04:52 Arch-PC systemd[607]: dbus.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed D-Bus User Message Bus Socket.
mai 14 15:04:52 Arch-PC systemd[607]: dirmngr.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed GnuPG network certificate management daemon.
mai 14 15:04:52 Arch-PC systemd[607]: gpg-agent-browser.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 15:04:52 Arch-PC systemd[607]: gpg-agent-extra.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 15:04:52 Arch-PC systemd[607]: gpg-agent-ssh.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed GnuPG cryptographic agent (ssh-agent emulation).
mai 14 15:04:52 Arch-PC systemd[607]: gpg-agent.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed GnuPG cryptographic agent and passphrase cache.
mai 14 15:04:52 Arch-PC systemd[607]: p11-kit-server.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed p11-kit server.
mai 14 15:04:52 Arch-PC systemd[607]: pipewire.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed Multimedia System.
mai 14 15:04:52 Arch-PC systemd[607]: pulseaudio.socket: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Closed Sound System.
mai 14 15:04:52 Arch-PC systemd[607]: Reached target Shutdown.
mai 14 15:04:52 Arch-PC systemd[607]: systemd-exit.service: Succeeded.
mai 14 15:04:52 Arch-PC systemd[607]: Finished Exit the Session.
mai 14 15:04:52 Arch-PC systemd[607]: Reached target Exit the Session.
mai 14 15:04:52 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:52 Arch-PC systemd[1]: user@977.service: Succeeded.
mai 14 15:04:52 Arch-PC systemd[609]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
mai 14 15:04:52 Arch-PC systemd[1]: Stopped User Manager for UID 977.
mai 14 15:04:52 Arch-PC systemd[1]: Stopping User Runtime Directory /run/user/977...
mai 14 15:04:52 Arch-PC kernel: audit: type=1131 audit(1589479492.319:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:52 Arch-PC systemd[1]: run-user-977.mount: Succeeded.
mai 14 15:04:52 Arch-PC systemd[1]: user-runtime-dir@977.service: Succeeded.
mai 14 15:04:52 Arch-PC systemd[1]: Stopped User Runtime Directory /run/user/977.
mai 14 15:04:52 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:52 Arch-PC kernel: audit: type=1131 audit(1589479492.342:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@977 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:04:52 Arch-PC systemd[1]: Removed slice User Slice of UID 977.
mai 14 15:04:56 Arch-PC emby-server[509]: Info Skia: SkiaSharp version: 1.68.0.0
mai 14 15:04:56 Arch-PC emby-server[509]: Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 05/15/2020 02:00:00, which is 655.0570579433333 minutes from now.
mai 14 15:04:56 Arch-PC emby-server[509]: Info TaskManager: Daily trigger for Rotate log file set to fire at 05/15/2020 00:00:00, which is 535.0546562883334 minutes from now.
mai 14 15:04:56 Arch-PC emby-server[509]: Info App: ServerId: 8e7e254f5c794322ae147b1029f81496
mai 14 15:04:56 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Init BeginReceive on 0.0.0.0
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.2204794 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Loading data from /var/lib/emby/data/connect.txt
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Loading data from /var/lib/emby/data/wan.dat
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0096588 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Core startup complete
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Post-init migrations complete
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0007289 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Security.PluginSecurityManager
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 5.34E-05 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0001428 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point NfoMetadata.EntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0005572 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Webhooks.WebhooksEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Webhooks.WebhooksEntryPoint. Duration: 0.0026977 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 5.53E-05 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0016932 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistsEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistsEntryPoint. Duration: 0.0012708 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0002362 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0007218 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup
mai 14 15:04:57 Arch-PC nmbd[596]: [2020/05/14 15:04:57.600092, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
mai 14 15:04:57 Arch-PC nmbd[596]: *****
mai 14 15:04:57 Arch-PC nmbd[596]:
mai 14 15:04:57 Arch-PC nmbd[596]: Samba name server ARCH-PC is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.50
mai 14 15:04:57 Arch-PC nmbd[596]:
mai 14 15:04:57 Arch-PC nmbd[596]: *****
mai 14 15:04:57 Arch-PC emby-server[509]: Info HttpClient: GET https://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.7345832 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0004091 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0001875 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0023021 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0035539 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0005341 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0005914 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0002035 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0057287 seconds
mai 14 15:04:57 Arch-PC emby-server[509]: Info App: Starting entry point Emby.LiveTV.EntryPoint
mai 14 15:04:57 Arch-PC emby-server[509]: Info LiveTV: Loading live tv data from /var/lib/emby/data/livetv/timers
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0271027 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.LiveTV.LiveTVEntryPoint
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.LiveTV.LiveTVEntryPoint. Duration: 0.0002672 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.LiveTV.RecordingNotifier
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0031165 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0050748 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.372038 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Notifications.Notifications
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0010999 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: SyncRepository Initialize taking write lock
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: SyncRepository Initialize write lock taken
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0077756 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0023635 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0003533 seconds
mai 14 15:04:58 Arch-PC emby-server[509]: Info App: All entry points have started
mai 14 15:05:01 Arch-PC java[510]: 2020-05-14 15:05:01,807 INFO lm.tools - Initialized tool: Magick. Executable: /usr/bin/magick. Version: ImageMagick 7.0.10-11 Q16 x86_64 2020-05-12 https://imagemagick.org.
mai 14 15:05:03 Arch-PC java[510]: 2020-05-14 15:05:03,568 INFO lm.tools - Initialized tool: FFprobe. Executable: /home/stalker/limbomedia/tools/ffmpeg/ffprobe. Version: ffprobe version 4.2.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2007-2019 the FFmpeg developers.
mai 14 15:05:04 Arch-PC java[510]: 2020-05-14 15:05:04,971 INFO lm.tools - Initialized tool: FFmpeg. Executable: /home/stalker/limbomedia/tools/ffmpeg/ffmpeg. Version: ffmpeg version 4.2.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2019 the FFmpeg developers.
mai 14 15:05:05 Arch-PC java[510]: 2020-05-14 15:05:05,015 INFO lm.system - CORE initialization started for LimboMedia Server Version 2.15. Instance name: LimboMedia
mai 14 15:05:05 Arch-PC java[510]: 2020-05-14 15:05:05,028 INFO lm.system - Checking/Initializing scheduler and registering jobs.
mai 14 15:05:05 Arch-PC java[510]: 2020-05-14 15:05:05,044 INFO lm.system - CORE initialization finished. Starting adapters now (http, dlna/upnp, api) ...
mai 14 15:05:05 Arch-PC java[510]: 2020-05-14 15:05:05,276 WARN lm.system.cert - Initializing certificate provider fallback. It's not secure and leads to browser warnings. If you use HTTPS you should really configure another real provider.
mai 14 15:05:05 Arch-PC java[510]: 2020-05-14 15:05:05,357 INFO lm.tools - Initialized tool: Shell (Bash). Executable: /usr/bin/bash. Version: GNU bash, versão 5.0.16(1)-release (x86_64-pc-linux-gnu).
mai 14 15:05:05 Arch-PC java[510]: 2020-05-14 15:05:05,967 INFO lm.system - Starting module web -> Webserver HTTP(S) for Webinterface, API, UPnP Mediastreaming.
mai 14 15:05:07 Arch-PC java[510]: 2020-05-14 15:05:07,268 INFO lm.web - Initialized local network security. Mapping anonymous requests (by UPnP/DLNA) to user 'LAN', restricted to netmasks 255.255.255.0(IPv4) and ffff:ffff:ffff:ff00::(IPv6).
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,044 INFO lm.web - Connector HTTP [http/1.1] started on *:8000 --> Visit http://192.168.0.50:8000
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,168 INFO lm.web - Connector HTTPS [ssl, http/1.1] started on *:8001 --> Visit https://192.168.0.50:8001
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,202 INFO lm.system - Starting module upnp -> UPnP/DLNA discovery and directory browsing.
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - ============================================================
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - Startup complete. Welcome to
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - __ _ __ __ ___ ___
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - / / (_)___ ___ / /_ ____ / |/ /__ ____/ (_)___ _
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - / / / / __ `__ \/ __ \/ __ \/ /|_/ / _ \/ __ / / __ `/
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - / /___/ / / / / / / /_/ / /_/ / / / / __/ /_/ / / /_/ /
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - /_____/_/_/ /_/ /_/_.___/\____/_/ /_/\___/\__,_/_/\__,_/
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - Version: 2.15 - Stamp: 202003032024
mai 14 15:05:08 Arch-PC java[510]: 2020-05-14 15:05:08,504 INFO lm.system - ============================================================
mai 14 15:05:32 Arch-PC kernel: audit: type=1130 audit(1589479532.302:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:32 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 15:05:32 Arch-PC systemd[1]: Started Getty on tty2.
mai 14 15:05:42 Arch-PC audit[755]: USER_AUTH pid=755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC kernel: audit: type=1100 audit(1589479542.442:65): pid=755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC audit[755]: USER_ACCT pid=755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC kernel: audit: type=1101 audit(1589479542.535:66): pid=755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC audit[755]: CRED_ACQ pid=755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC kernel: audit: type=1103 audit(1589479542.539:67): pid=755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC kernel: audit: type=1006 audit(1589479542.539:68): pid=755 uid=0 old-auid=4294967295 auid=1003 tty=tty2 old-ses=4294967295 ses=2 res=1
mai 14 15:05:42 Arch-PC login[755]: pam_unix(login:session): session opened for user stalker by LOGIN(uid=0)
mai 14 15:05:42 Arch-PC systemd[1]: Created slice User Slice of UID 1003.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/1003...
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 15:05:42 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 15:05:42 Arch-PC systemd-logind[499]: New session 2 of user stalker.
mai 14 15:05:42 Arch-PC kernel: audit: type=1130 audit(1589479542.569:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/1003.
mai 14 15:05:42 Arch-PC systemd[1]: Starting User Manager for UID 1003...
mai 14 15:05:42 Arch-PC audit[758]: USER_ACCT pid=758 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC audit[758]: CRED_ACQ pid=758 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 15:05:42 Arch-PC systemd[758]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[stalker] ruser=[<unknown>] rhost=[<unknown>]
mai 14 15:05:42 Arch-PC systemd[758]: pam_unix(systemd-user:session): session opened for user stalker by (uid=0)
mai 14 15:05:42 Arch-PC kernel: audit: type=1101 audit(1589479542.575:70): pid=758 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC kernel: audit: type=1103 audit(1589479542.575:71): pid=758 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 15:05:42 Arch-PC kernel: audit: type=1006 audit(1589479542.575:72): pid=758 uid=0 old-auid=4294967295 auid=1003 tty=(none) old-ses=4294967295 ses=3 res=1
mai 14 15:05:42 Arch-PC audit[758]: USER_START pid=758 uid=0 auid=1003 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC kernel: audit: type=1105 audit(1589479542.579:73): pid=758 uid=0 auid=1003 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC audit: AUDIT1334 prog-id=15 op=LOAD
mai 14 15:05:42 Arch-PC kernel: audit: type=1334 audit(1589479542.582:74): prog-id=15 op=LOAD
mai 14 15:05:42 Arch-PC audit: AUDIT1334 prog-id=15 op=UNLOAD
mai 14 15:05:42 Arch-PC systemd[758]: Reached target Paths.
mai 14 15:05:42 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 15:05:42 Arch-PC audit[755]: USER_START pid=755 uid=0 auid=1003 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC audit[755]: CRED_REFR pid=755 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty2 res=success'
mai 14 15:05:42 Arch-PC systemd[758]: Reached target Timers.
mai 14 15:05:42 Arch-PC login[755]: LOGIN ON tty2 BY stalker
mai 14 15:05:42 Arch-PC systemd[758]: Starting D-Bus User Message Bus Socket.
mai 14 15:05:42 Arch-PC systemd[758]: Listening on GnuPG network certificate management daemon.
mai 14 15:05:42 Arch-PC systemd[758]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 15:05:42 Arch-PC systemd[758]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 15:05:42 Arch-PC systemd[758]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 15:05:42 Arch-PC systemd[758]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 15:05:42 Arch-PC systemd[758]: Listening on p11-kit server.
mai 14 15:05:42 Arch-PC systemd[758]: Listening on Multimedia System.
mai 14 15:05:42 Arch-PC systemd[758]: Listening on Sound System.
mai 14 15:05:42 Arch-PC systemd[758]: Listening on D-Bus User Message Bus Socket.
mai 14 15:05:42 Arch-PC systemd[758]: Reached target Sockets.
mai 14 15:05:42 Arch-PC systemd[758]: Reached target Basic System.
mai 14 15:05:42 Arch-PC systemd[1]: Started User Manager for UID 1003.
mai 14 15:05:42 Arch-PC systemd[758]: Starting Update XDG user dir configuration...
mai 14 15:05:42 Arch-PC systemd[1]: Started Session 2 of user stalker.
mai 14 15:05:42 Arch-PC systemd[758]: xdg-user-dirs-update.service: Succeeded.
mai 14 15:05:42 Arch-PC systemd[758]: Finished Update XDG user dir configuration.
mai 14 15:05:42 Arch-PC systemd[758]: Reached target Main User Target.
mai 14 15:05:42 Arch-PC systemd[758]: Startup finished in 223ms.
mai 14 15:06:30 Arch-PC audit[783]: USER_AUTH pid=783 uid=1003 auid=1003 ses=2 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC sudo[783]: stalker : TTY=tty2 ; PWD=/home/stalker ; USER=root ; COMMAND=/usr/bin/journalctl -b --no-pager
mai 14 15:06:30 Arch-PC kernel: kauditd_printk_skb: 4 callbacks suppressed
mai 14 15:06:30 Arch-PC kernel: audit: type=1100 audit(1589479590.032:79): pid=783 uid=1003 auid=1003 ses=2 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC sudo[783]: pam_unix(sudo:session): session opened for user root by stalker(uid=0)
mai 14 15:06:30 Arch-PC audit[783]: USER_ACCT pid=783 uid=1003 auid=1003 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC audit[783]: CRED_REFR pid=783 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC audit[783]: USER_START pid=783 uid=0 auid=1003 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC kernel: audit: type=1101 audit(1589479590.032:80): pid=783 uid=1003 auid=1003 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC kernel: audit: type=1110 audit(1589479590.035:81): pid=783 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 15:06:30 Arch-PC kernel: audit: type=1105 audit(1589479590.035:82): pid=783 uid=0 auid=1003 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'I even tried to start plasma with gdm login manager without success. I only get a black screen with cursor after I type my password and press enter, kapplymousethem, klauncher and kded5 have core dumped:
-- Logs begin at Sat 2020-05-09 19:06:46 -03, end at Thu 2020-05-14 14:35:25 -03. --
mai 14 14:15:09 Arch-PC kernel: microcode: microcode updated early to revision 0x27, date = 2019-02-26
mai 14 14:15:09 Arch-PC kernel: Linux version 5.6.12-arch1-1 (linux@archlinux) (gcc version 10.1.0 (GCC)) #1 SMP PREEMPT Sun, 10 May 2020 10:43:42 +0000
mai 14 14:15:09 Arch-PC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81 rw scsi_mod.use_blk_mq=1
mai 14 14:15:09 Arch-PC kernel: KERNEL supported cpus:
mai 14 14:15:09 Arch-PC kernel: Intel GenuineIntel
mai 14 14:15:09 Arch-PC kernel: AMD AuthenticAMD
mai 14 14:15:09 Arch-PC kernel: Hygon HygonGenuine
mai 14 14:15:09 Arch-PC kernel: Centaur CentaurHauls
mai 14 14:15:09 Arch-PC kernel: zhaoxin Shanghai
mai 14 14:15:09 Arch-PC kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
mai 14 14:15:09 Arch-PC kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
mai 14 14:15:09 Arch-PC kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
mai 14 14:15:09 Arch-PC kernel: BIOS-provided physical RAM map:
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c955cfff] usable
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000c955d000-0x00000000c9563fff] ACPI NVS
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000c9564000-0x00000000c9e5dfff] usable
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000c9e5e000-0x00000000ca0c6fff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000ca0c7000-0x00000000db8b3fff] usable
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000db8b4000-0x00000000dbc21fff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000dbc22000-0x00000000dbc5cfff] usable
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000dbc5d000-0x00000000dbd1efff] ACPI NVS
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000dbd1f000-0x00000000dcffefff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000dcfff000-0x00000000dcffffff] usable
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000dd800000-0x00000000df9fffff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
mai 14 14:15:09 Arch-PC kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021e5fffff] usable
mai 14 14:15:09 Arch-PC kernel: NX (Execute Disable) protection: active
mai 14 14:15:09 Arch-PC kernel: SMBIOS 2.7 present.
mai 14 14:15:09 Arch-PC kernel: DMI: Gigabyte Technology Co., Ltd. B85M-D3PH/B85M-D3PH, BIOS F4 07/04/2014
mai 14 14:15:09 Arch-PC kernel: tsc: Fast TSC calibration using PIT
mai 14 14:15:09 Arch-PC kernel: tsc: Detected 2693.955 MHz processor
mai 14 14:15:09 Arch-PC kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
mai 14 14:15:09 Arch-PC kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
mai 14 14:15:09 Arch-PC kernel: last_pfn = 0x21e600 max_arch_pfn = 0x400000000
mai 14 14:15:09 Arch-PC kernel: MTRR default type: uncachable
mai 14 14:15:09 Arch-PC kernel: MTRR fixed ranges enabled:
mai 14 14:15:09 Arch-PC kernel: 00000-9FFFF write-back
mai 14 14:15:09 Arch-PC kernel: A0000-BFFFF uncachable
mai 14 14:15:09 Arch-PC kernel: C0000-CFFFF write-protect
mai 14 14:15:09 Arch-PC kernel: D0000-E7FFF uncachable
mai 14 14:15:09 Arch-PC kernel: E8000-FFFFF write-protect
mai 14 14:15:09 Arch-PC kernel: MTRR variable ranges enabled:
mai 14 14:15:09 Arch-PC kernel: 0 base 0000000000 mask 7E00000000 write-back
mai 14 14:15:09 Arch-PC kernel: 1 base 0200000000 mask 7FE0000000 write-back
mai 14 14:15:09 Arch-PC kernel: 2 base 00E0000000 mask 7FE0000000 uncachable
mai 14 14:15:09 Arch-PC kernel: 3 base 00DE000000 mask 7FFE000000 uncachable
mai 14 14:15:09 Arch-PC kernel: 4 base 00DD800000 mask 7FFF800000 uncachable
mai 14 14:15:09 Arch-PC kernel: 5 base 021F000000 mask 7FFF000000 uncachable
mai 14 14:15:09 Arch-PC kernel: 6 base 021E800000 mask 7FFF800000 uncachable
mai 14 14:15:09 Arch-PC kernel: 7 base 021E600000 mask 7FFFE00000 uncachable
mai 14 14:15:09 Arch-PC kernel: 8 disabled
mai 14 14:15:09 Arch-PC kernel: 9 disabled
mai 14 14:15:09 Arch-PC kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
mai 14 14:15:09 Arch-PC kernel: total RAM covered: 8126M
mai 14 14:15:09 Arch-PC kernel: Found optimal setting for mtrr clean up
mai 14 14:15:09 Arch-PC kernel: gran_size: 64K chunk_size: 64M num_reg: 10 lose cover RAM: 0G
mai 14 14:15:09 Arch-PC kernel: e820: update [mem 0xdd800000-0xffffffff] usable ==> reserved
mai 14 14:15:09 Arch-PC kernel: last_pfn = 0xdd000 max_arch_pfn = 0x400000000
mai 14 14:15:09 Arch-PC kernel: found SMP MP-table at [mem 0x000fd6d0-0x000fd6df]
mai 14 14:15:09 Arch-PC kernel: check: Scanning 1 areas for low memory corruption
mai 14 14:15:09 Arch-PC kernel: Using GB pages for direct mapping
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd401000, 0x1fd401fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd402000, 0x1fd402fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd403000, 0x1fd403fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd404000, 0x1fd404fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd405000, 0x1fd405fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd406000, 0x1fd406fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd407000, 0x1fd407fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd408000, 0x1fd408fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd409000, 0x1fd409fff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd40a000, 0x1fd40afff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd40b000, 0x1fd40bfff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: BRK [0x1fd40c000, 0x1fd40cfff] PGTABLE
mai 14 14:15:09 Arch-PC kernel: RAMDISK: [mem 0x367eb000-0x373ecfff]
mai 14 14:15:09 Arch-PC kernel: ACPI: Early table checksum verification disabled
mai 14 14:15:09 Arch-PC kernel: ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA)
mai 14 14:15:09 Arch-PC kernel: ACPI: XSDT 0x00000000DBCEB078 00006C (v01 ALASKA A M I 01072009 AMI 00010013)
mai 14 14:15:09 Arch-PC kernel: ACPI: FACP 0x00000000DBCF7E08 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
mai 14 14:15:09 Arch-PC kernel: ACPI: DSDT 0x00000000DBCEB178 00CC8D (v02 ALASKA A M I 00000088 INTL 20091112)
mai 14 14:15:09 Arch-PC kernel: ACPI: FACS 0x00000000DBD1D080 000040
mai 14 14:15:09 Arch-PC kernel: ACPI: APIC 0x00000000DBCF7F18 000062 (v03 ALASKA A M I 01072009 AMI 00010013)
mai 14 14:15:09 Arch-PC kernel: ACPI: FPDT 0x00000000DBCF7F80 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF7FC8 000539 (v01 PmRef Cpu0Ist 00003000 INTL 20120711)
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF8508 000AD8 (v01 PmRef CpuPm 00003000 INTL 20120711)
mai 14 14:15:09 Arch-PC kernel: ACPI: MCFG 0x00000000DBCF8FE0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
mai 14 14:15:09 Arch-PC kernel: ACPI: HPET 0x00000000DBCF9020 000038 (v01 ALASKA A M I 01072009 AMI. 00000005)
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF9058 00036D (v01 SataRe SataTabl 00001000 INTL 20120711)
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0x00000000DBCF93C8 0034E1 (v01 SaSsdt SaSsdt 00003000 INTL 20091112)
mai 14 14:15:09 Arch-PC kernel: ACPI: Local APIC address 0xfee00000
mai 14 14:15:09 Arch-PC kernel: No NUMA configuration found
mai 14 14:15:09 Arch-PC kernel: Faking a node at [mem 0x0000000000000000-0x000000021e5fffff]
mai 14 14:15:09 Arch-PC kernel: NODE_DATA(0) allocated [mem 0x21e5fc000-0x21e5fffff]
mai 14 14:15:09 Arch-PC kernel: Zone ranges:
mai 14 14:15:09 Arch-PC kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
mai 14 14:15:09 Arch-PC kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
mai 14 14:15:09 Arch-PC kernel: Normal [mem 0x0000000100000000-0x000000021e5fffff]
mai 14 14:15:09 Arch-PC kernel: Device empty
mai 14 14:15:09 Arch-PC kernel: Movable zone start for each node
mai 14 14:15:09 Arch-PC kernel: Early memory node ranges
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x0000000000001000-0x000000000009cfff]
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x0000000000100000-0x00000000c955cfff]
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x00000000c9564000-0x00000000c9e5dfff]
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x00000000ca0c7000-0x00000000db8b3fff]
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x00000000dbc22000-0x00000000dbc5cfff]
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x00000000dcfff000-0x00000000dcffffff]
mai 14 14:15:09 Arch-PC kernel: node 0: [mem 0x0000000100000000-0x000000021e5fffff]
mai 14 14:15:09 Arch-PC kernel: Zeroed struct page in unavailable ranges: 25572 pages
mai 14 14:15:09 Arch-PC kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000021e5fffff]
mai 14 14:15:09 Arch-PC kernel: On node 0 totalpages: 2071580
mai 14 14:15:09 Arch-PC kernel: DMA zone: 64 pages used for memmap
mai 14 14:15:09 Arch-PC kernel: DMA zone: 21 pages reserved
mai 14 14:15:09 Arch-PC kernel: DMA zone: 3996 pages, LIFO batch:0
mai 14 14:15:09 Arch-PC kernel: DMA32 zone: 13978 pages used for memmap
mai 14 14:15:09 Arch-PC kernel: DMA32 zone: 894592 pages, LIFO batch:63
mai 14 14:15:09 Arch-PC kernel: Normal zone: 18328 pages used for memmap
mai 14 14:15:09 Arch-PC kernel: Normal zone: 1172992 pages, LIFO batch:63
mai 14 14:15:09 Arch-PC kernel: Reserving Intel graphics memory at [mem 0xdda00000-0xdf9fffff]
mai 14 14:15:09 Arch-PC kernel: ACPI: PM-Timer IO Port: 0x1808
mai 14 14:15:09 Arch-PC kernel: ACPI: Local APIC address 0xfee00000
mai 14 14:15:09 Arch-PC kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
mai 14 14:15:09 Arch-PC kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
mai 14 14:15:09 Arch-PC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
mai 14 14:15:09 Arch-PC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
mai 14 14:15:09 Arch-PC kernel: ACPI: IRQ0 used by override.
mai 14 14:15:09 Arch-PC kernel: ACPI: IRQ9 used by override.
mai 14 14:15:09 Arch-PC kernel: Using ACPI (MADT) for SMP configuration information
mai 14 14:15:09 Arch-PC kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
mai 14 14:15:09 Arch-PC kernel: smpboot: Allowing 2 CPUs, 0 hotplug CPUs
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000dffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x000e0000-0x000fffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xc955d000-0xc9563fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xc9e5e000-0xca0c6fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdb8b4000-0xdbc21fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdbc5d000-0xdbd1efff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdbd1f000-0xdcffefff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdd000000-0xdd7fffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdd800000-0xdf9fffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdfa00000-0xf7ffffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
mai 14 14:15:09 Arch-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
mai 14 14:15:09 Arch-PC kernel: [mem 0xdfa00000-0xf7ffffff] available for PCI devices
mai 14 14:15:09 Arch-PC kernel: Booting paravirtualized kernel on bare hardware
mai 14 14:15:09 Arch-PC kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
mai 14 14:15:09 Arch-PC kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:2 nr_node_ids:1
mai 14 14:15:09 Arch-PC kernel: percpu: Embedded 57 pages/cpu s196608 r8192 d28672 u1048576
mai 14 14:15:09 Arch-PC kernel: pcpu-alloc: s196608 r8192 d28672 u1048576 alloc=1*2097152
mai 14 14:15:09 Arch-PC kernel: pcpu-alloc: [0] 0 1
mai 14 14:15:09 Arch-PC kernel: Built 1 zonelists, mobility grouping on. Total pages: 2039189
mai 14 14:15:09 Arch-PC kernel: Policy zone: Normal
mai 14 14:15:09 Arch-PC kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81 rw scsi_mod.use_blk_mq=1
mai 14 14:15:09 Arch-PC kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: mem auto-init: stack:byref_all, heap alloc:on, heap free:off
mai 14 14:15:09 Arch-PC kernel: Memory: 8033364K/8286320K available (12291K kernel code, 1462K rwdata, 4464K rodata, 1608K init, 3184K bss, 252956K reserved, 0K cma-reserved)
mai 14 14:15:09 Arch-PC kernel: random: get_random_u64 called from __kmem_cache_create+0x3e/0x610 with crng_init=0
mai 14 14:15:09 Arch-PC kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
mai 14 14:15:09 Arch-PC kernel: Kernel/User page tables isolation: enabled
mai 14 14:15:09 Arch-PC kernel: ftrace: allocating 39094 entries in 153 pages
mai 14 14:15:09 Arch-PC kernel: ftrace: allocated 153 pages with 4 groups
mai 14 14:15:09 Arch-PC kernel: rcu: Preemptible hierarchical RCU implementation.
mai 14 14:15:09 Arch-PC kernel: rcu: RCU dyntick-idle grace-period acceleration is enabled.
mai 14 14:15:09 Arch-PC kernel: rcu: RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=2.
mai 14 14:15:09 Arch-PC kernel: rcu: RCU priority boosting: priority 1 delay 500 ms.
mai 14 14:15:09 Arch-PC kernel: Tasks RCU enabled.
mai 14 14:15:09 Arch-PC kernel: rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.
mai 14 14:15:09 Arch-PC kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
mai 14 14:15:09 Arch-PC kernel: NR_IRQS: 20736, nr_irqs: 440, preallocated irqs: 16
mai 14 14:15:09 Arch-PC kernel: spurious 8259A interrupt: IRQ7.
mai 14 14:15:09 Arch-PC kernel: Console: colour dummy device 80x25
mai 14 14:15:09 Arch-PC kernel: printk: console [tty0] enabled
mai 14 14:15:09 Arch-PC kernel: ACPI: Core revision 20200110
mai 14 14:15:09 Arch-PC kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
mai 14 14:15:09 Arch-PC kernel: APIC: Switch to symmetric I/O mode setup
mai 14 14:15:09 Arch-PC kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
mai 14 14:15:09 Arch-PC kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x26d4f01859b, max_idle_ns: 440795341120 ns
mai 14 14:15:09 Arch-PC kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5390.40 BogoMIPS (lpj=8979850)
mai 14 14:15:09 Arch-PC kernel: pid_max: default: 32768 minimum: 301
mai 14 14:15:09 Arch-PC kernel: LSM: Security Framework initializing
mai 14 14:15:09 Arch-PC kernel: Yama: becoming mindful.
mai 14 14:15:09 Arch-PC kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE tmpfs ***
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE proc ***
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE cgroup ***
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE cgroup2 ***
mai 14 14:15:09 Arch-PC kernel: mce: CPU0: Thermal monitoring enabled (TM1)
mai 14 14:15:09 Arch-PC kernel: process: using mwait in idle threads
mai 14 14:15:09 Arch-PC kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
mai 14 14:15:09 Arch-PC kernel: Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
mai 14 14:15:09 Arch-PC kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
mai 14 14:15:09 Arch-PC kernel: Spectre V2 : Mitigation: Full generic retpoline
mai 14 14:15:09 Arch-PC kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
mai 14 14:15:09 Arch-PC kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
mai 14 14:15:09 Arch-PC kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
mai 14 14:15:09 Arch-PC kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
mai 14 14:15:09 Arch-PC kernel: MDS: Mitigation: Clear CPU buffers
mai 14 14:15:09 Arch-PC kernel: Freeing SMP alternatives memory: 32K
mai 14 14:15:09 Arch-PC kernel: TSC deadline timer enabled
mai 14 14:15:09 Arch-PC kernel: smpboot: CPU0: Intel(R) Celeron(R) CPU G1820 @ 2.70GHz (family: 0x6, model: 0x3c, stepping: 0x3)
mai 14 14:15:09 Arch-PC kernel: Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
mai 14 14:15:09 Arch-PC kernel: ... version: 3
mai 14 14:15:09 Arch-PC kernel: ... bit width: 48
mai 14 14:15:09 Arch-PC kernel: ... generic registers: 8
mai 14 14:15:09 Arch-PC kernel: ... value mask: 0000ffffffffffff
mai 14 14:15:09 Arch-PC kernel: ... max period: 00007fffffffffff
mai 14 14:15:09 Arch-PC kernel: ... fixed-purpose events: 3
mai 14 14:15:09 Arch-PC kernel: ... event mask: 00000007000000ff
mai 14 14:15:09 Arch-PC kernel: rcu: Hierarchical SRCU implementation.
mai 14 14:15:09 Arch-PC kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
mai 14 14:15:09 Arch-PC kernel: smp: Bringing up secondary CPUs ...
mai 14 14:15:09 Arch-PC kernel: x86: Booting SMP configuration:
mai 14 14:15:09 Arch-PC kernel: .... node #0, CPUs: #1
mai 14 14:15:09 Arch-PC kernel: smp: Brought up 1 node, 2 CPUs
mai 14 14:15:09 Arch-PC kernel: smpboot: Max logical packages: 1
mai 14 14:15:09 Arch-PC kernel: smpboot: Total of 2 processors activated (10780.81 BogoMIPS)
mai 14 14:15:09 Arch-PC kernel: devtmpfs: initialized
mai 14 14:15:09 Arch-PC kernel: x86/mm: Memory block size: 128MB
mai 14 14:15:09 Arch-PC kernel: PM: Registering ACPI NVS region [mem 0xc955d000-0xc9563fff] (28672 bytes)
mai 14 14:15:09 Arch-PC kernel: PM: Registering ACPI NVS region [mem 0xdbc5d000-0xdbd1efff] (794624 bytes)
mai 14 14:15:09 Arch-PC kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
mai 14 14:15:09 Arch-PC kernel: futex hash table entries: 512 (order: 3, 32768 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: pinctrl core: initialized pinctrl subsystem
mai 14 14:15:09 Arch-PC kernel: PM: RTC time: 17:15:02, date: 2020-05-14
mai 14 14:15:09 Arch-PC kernel: thermal_sys: Registered thermal governor 'fair_share'
mai 14 14:15:09 Arch-PC kernel: thermal_sys: Registered thermal governor 'bang_bang'
mai 14 14:15:09 Arch-PC kernel: thermal_sys: Registered thermal governor 'step_wise'
mai 14 14:15:09 Arch-PC kernel: thermal_sys: Registered thermal governor 'user_space'
mai 14 14:15:09 Arch-PC kernel: thermal_sys: Registered thermal governor 'power_allocator'
mai 14 14:15:09 Arch-PC kernel: NET: Registered protocol family 16
mai 14 14:15:09 Arch-PC kernel: audit: initializing netlink subsys (disabled)
mai 14 14:15:09 Arch-PC kernel: audit: type=2000 audit(1589476502.116:1): state=initialized audit_enabled=0 res=1
mai 14 14:15:09 Arch-PC kernel: cpuidle: using governor ladder
mai 14 14:15:09 Arch-PC kernel: cpuidle: using governor menu
mai 14 14:15:09 Arch-PC kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
mai 14 14:15:09 Arch-PC kernel: ACPI: bus type PCI registered
mai 14 14:15:09 Arch-PC kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
mai 14 14:15:09 Arch-PC kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
mai 14 14:15:09 Arch-PC kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
mai 14 14:15:09 Arch-PC kernel: PCI: Using configuration type 1 for base access
mai 14 14:15:09 Arch-PC kernel: core: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
mai 14 14:15:09 Arch-PC kernel: HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
mai 14 14:15:09 Arch-PC kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(Module Device)
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(Processor Device)
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(Processor Aggregator Device)
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(Linux-Dell-Video)
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
mai 14 14:15:09 Arch-PC kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
mai 14 14:15:09 Arch-PC kernel: ACPI: 5 ACPI AML tables successfully acquired and loaded
mai 14 14:15:09 Arch-PC kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
mai 14 14:15:09 Arch-PC kernel: ACPI: Dynamic OEM Table Load:
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0xFFFF9A61953D4C00 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
mai 14 14:15:09 Arch-PC kernel: ACPI: Dynamic OEM Table Load:
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0xFFFF9A61953C4800 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
mai 14 14:15:09 Arch-PC kernel: ACPI: Dynamic OEM Table Load:
mai 14 14:15:09 Arch-PC kernel: ACPI: SSDT 0xFFFF9A619483CA00 000119 (v01 PmRef ApCst 00003000 INTL 20120711)
mai 14 14:15:09 Arch-PC kernel: ACPI: Interpreter enabled
mai 14 14:15:09 Arch-PC kernel: ACPI: (supports S0 S3 S4 S5)
mai 14 14:15:09 Arch-PC kernel: ACPI: Using IOAPIC for interrupt routing
mai 14 14:15:09 Arch-PC kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
mai 14 14:15:09 Arch-PC kernel: ACPI: Enabled 7 GPEs in block 00 to 3F
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Resource [FN00] (off)
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Resource [FN01] (off)
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Resource [FN02] (off)
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Resource [FN03] (off)
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Resource [FN04] (off)
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
mai 14 14:15:09 Arch-PC kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
mai 14 14:15:09 Arch-PC kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug PME]
mai 14 14:15:09 Arch-PC kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability LTR]
mai 14 14:15:09 Arch-PC kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
mai 14 14:15:09 Arch-PC kernel: PCI host bridge to bus 0000:00
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [mem 0xdfa00000-0xfeafffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:00.0: [8086:0c00] type 00 class 0x060000
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: [8086:0402] type 00 class 0x030000
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7800000-0xf7bfffff 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:03.0: reg 0x10: [mem 0xf7d14000-0xf7d17fff 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7d00000-0xf7d0ffff 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7d1f000-0xf7d1f00f 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:16.3: [8086:8c3d] type 00 class 0x070002
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:16.3: reg 0x10: [io 0xf0c0-0xf0c7]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:16.3: reg 0x14: [mem 0xf7d1d000-0xf7d1dfff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7d1c000-0xf7d1c3ff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7d10000-0xf7d13fff 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.1: [8086:8c12] type 01 class 0x060400
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: [8086:8c14] type 01 class 0x060400
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7d1b000-0xf7d1b3ff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.0: [8086:8c50] type 00 class 0x060100
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: [8086:8c02] type 00 class 0x010601
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0b0-0xf0b7]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0a0-0xf0a3]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf090-0xf097]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf080-0xf083]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7d1a000-0xf7d1a7ff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.2: PME# supported from D3hot
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7d19000-0xf7d190ff 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
mai 14 14:15:09 Arch-PC kernel: pci 0000:02:00.0: [8086:244e] type 01 class 0x060401
mai 14 14:15:09 Arch-PC kernel: pci 0000:02:00.0: supports D1 D2
mai 14 14:15:09 Arch-PC kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.1: PCI bridge to [bus 02-03]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:03: extended config space not accessible
mai 14 14:15:09 Arch-PC kernel: pci 0000:02:00.0: PCI bridge to [bus 03] (subtractive decode)
mai 14 14:15:09 Arch-PC kernel: pci 0000:04:00.0: [10ec:8168] type 00 class 0x020000
mai 14 14:15:09 Arch-PC kernel: pci 0000:04:00.0: reg 0x10: [io 0xe000-0xe0ff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:04:00.0: reg 0x18: [mem 0xf7c00000-0xf7c00fff 64bit]
mai 14 14:15:09 Arch-PC kernel: pci 0000:04:00.0: reg 0x20: [mem 0xf0000000-0xf0003fff 64bit pref]
mai 14 14:15:09 Arch-PC kernel: pci 0000:04:00.0: supports D1 D2
mai 14 14:15:09 Arch-PC kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: PCI bridge to [bus 04]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: bridge window [io 0xe000-0xefff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf7c00000-0xf7cfffff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 10 11 12 14 15)
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 10 11 12 14 15)
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 10 11 12 14 15)
mai 14 14:15:09 Arch-PC kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
mai 14 14:15:09 Arch-PC kernel: iommu: Default domain type: Translated
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: vgaarb: bridge control possible
mai 14 14:15:09 Arch-PC kernel: vgaarb: loaded
mai 14 14:15:09 Arch-PC kernel: SCSI subsystem initialized
mai 14 14:15:09 Arch-PC kernel: libata version 3.00 loaded.
mai 14 14:15:09 Arch-PC kernel: ACPI: bus type USB registered
mai 14 14:15:09 Arch-PC kernel: usbcore: registered new interface driver usbfs
mai 14 14:15:09 Arch-PC kernel: usbcore: registered new interface driver hub
mai 14 14:15:09 Arch-PC kernel: usbcore: registered new device driver usb
mai 14 14:15:09 Arch-PC kernel: pps_core: LinuxPPS API ver. 1 registered
mai 14 14:15:09 Arch-PC kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
mai 14 14:15:09 Arch-PC kernel: PTP clock support registered
mai 14 14:15:09 Arch-PC kernel: EDAC MC: Ver: 3.0.0
mai 14 14:15:09 Arch-PC kernel: PCI: Using ACPI for IRQ routing
mai 14 14:15:09 Arch-PC kernel: PCI: pci_cache_line_size set to 64 bytes
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0xc955d000-0xcbffffff]
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0xc9e5e000-0xcbffffff]
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0xdb8b4000-0xdbffffff]
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0xdbc5d000-0xdbffffff]
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0xdd000000-0xdfffffff]
mai 14 14:15:09 Arch-PC kernel: e820: reserve RAM buffer [mem 0x21e600000-0x21fffffff]
mai 14 14:15:09 Arch-PC kernel: NetLabel: Initializing
mai 14 14:15:09 Arch-PC kernel: NetLabel: domain hash size = 128
mai 14 14:15:09 Arch-PC kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
mai 14 14:15:09 Arch-PC kernel: NetLabel: unlabeled traffic allowed by default
mai 14 14:15:09 Arch-PC kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
mai 14 14:15:09 Arch-PC kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
mai 14 14:15:09 Arch-PC kernel: clocksource: Switched to clocksource tsc-early
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE bpf ***
mai 14 14:15:09 Arch-PC kernel: VFS: Disk quotas dquot_6.6.0
mai 14 14:15:09 Arch-PC kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE ramfs ***
mai 14 14:15:09 Arch-PC kernel: *** VALIDATE hugetlbfs ***
mai 14 14:15:09 Arch-PC kernel: pnp: PnP ACPI init
mai 14 14:15:09 Arch-PC kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x0680-0x069f] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0xffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0xffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0xffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x1c00-0x1cfe] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x1d00-0x1dfe] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x1e00-0x1efe] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x1f00-0x1ffe] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x1800-0x18fe] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: [io 0x164e-0x164f] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 14:15:09 Arch-PC kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
mai 14 14:15:09 Arch-PC kernel: system 00:03: [io 0x1854-0x1857] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
mai 14 14:15:09 Arch-PC kernel: system 00:04: [io 0x0a00-0x0a0f] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:04: [io 0x0a30-0x0a3f] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:04: [io 0x0a20-0x0a2f] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 14:15:09 Arch-PC kernel: system 00:05: [io 0x04d0-0x04d1] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xf7fdf000-0xf7fdffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: [mem 0xf7fe0000-0xf7feffff] has been reserved
mai 14 14:15:09 Arch-PC kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
mai 14 14:15:09 Arch-PC kernel: pnp: PnP ACPI: found 7 devices
mai 14 14:15:09 Arch-PC kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
mai 14 14:15:09 Arch-PC kernel: pci 0000:02:00.0: PCI bridge to [bus 03]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.1: PCI bridge to [bus 02-03]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: PCI bridge to [bus 04]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: bridge window [io 0xe000-0xefff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf7c00000-0xf7cfffff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1c.2: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:00: resource 13 [mem 0xdfa00000-0xfeafffff window]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:04: resource 0 [io 0xe000-0xefff]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:04: resource 1 [mem 0xf7c00000-0xf7cfffff]
mai 14 14:15:09 Arch-PC kernel: pci_bus 0000:04: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref]
mai 14 14:15:09 Arch-PC kernel: NET: Registered protocol family 2
mai 14 14:15:09 Arch-PC kernel: tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: TCP: Hash tables configured (established 65536 bind 65536)
mai 14 14:15:09 Arch-PC kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
mai 14 14:15:09 Arch-PC kernel: NET: Registered protocol family 1
mai 14 14:15:09 Arch-PC kernel: NET: Registered protocol family 44
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x6d5 took 20028 usecs
mai 14 14:15:09 Arch-PC kernel: pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x6d5 took 19510 usecs
mai 14 14:15:09 Arch-PC kernel: PCI: CLS 64 bytes, default 64
mai 14 14:15:09 Arch-PC kernel: Trying to unpack rootfs image as initramfs...
mai 14 14:15:09 Arch-PC kernel: Freeing initrd memory: 12296K
mai 14 14:15:09 Arch-PC kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
mai 14 14:15:09 Arch-PC kernel: software IO TLB: mapped [mem 0xd78b4000-0xdb8b4000] (64MB)
mai 14 14:15:09 Arch-PC kernel: check: Scanning for low memory corruption every 60 seconds
mai 14 14:15:09 Arch-PC kernel: Initialise system trusted keyrings
mai 14 14:15:09 Arch-PC kernel: Key type blacklist registered
mai 14 14:15:09 Arch-PC kernel: workingset: timestamp_bits=41 max_order=21 bucket_order=0
mai 14 14:15:09 Arch-PC kernel: zbud: loaded
mai 14 14:15:09 Arch-PC kernel: Key type asymmetric registered
mai 14 14:15:09 Arch-PC kernel: Asymmetric key parser 'x509' registered
mai 14 14:15:09 Arch-PC kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
mai 14 14:15:09 Arch-PC kernel: io scheduler mq-deadline registered
mai 14 14:15:09 Arch-PC kernel: io scheduler kyber registered
mai 14 14:15:09 Arch-PC kernel: io scheduler bfq registered
mai 14 14:15:09 Arch-PC kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
mai 14 14:15:09 Arch-PC kernel: vesafb: mode is 1920x1080x32, linelength=7680, pages=0
mai 14 14:15:09 Arch-PC kernel: vesafb: scrolling: redraw
mai 14 14:15:09 Arch-PC kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
mai 14 14:15:09 Arch-PC kernel: vesafb: framebuffer at 0xe0000000, mapped to 0x000000003f75ece7, using 8128k, total 8128k
mai 14 14:15:09 Arch-PC kernel: fbcon: Deferring console take-over
mai 14 14:15:09 Arch-PC kernel: fb0: VESA VGA frame buffer device
mai 14 14:15:09 Arch-PC kernel: intel_idle: MWAIT substates: 0x2120
mai 14 14:15:09 Arch-PC kernel: intel_idle: v0.4.1 model 0x3C
mai 14 14:15:09 Arch-PC kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
mai 14 14:15:09 Arch-PC kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Button [PWRB]
mai 14 14:15:09 Arch-PC kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
mai 14 14:15:09 Arch-PC kernel: ACPI: Power Button [PWRF]
mai 14 14:15:09 Arch-PC kernel: thermal LNXTHERM:00: registered as thermal_zone0
mai 14 14:15:09 Arch-PC kernel: ACPI: Thermal Zone [TZ00] (28 C)
mai 14 14:15:09 Arch-PC kernel: thermal LNXTHERM:01: registered as thermal_zone1
mai 14 14:15:09 Arch-PC kernel: ACPI: Thermal Zone [TZ01] (30 C)
mai 14 14:15:09 Arch-PC kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
mai 14 14:15:09 Arch-PC kernel: 0000:00:16.3: ttyS0 at I/O 0xf0c0 (irq = 19, base_baud = 115200) is a 16550A
mai 14 14:15:09 Arch-PC kernel: AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
mai 14 14:15:09 Arch-PC kernel: AMD-Vi: AMD IOMMUv2 functionality not available on this system
mai 14 14:15:09 Arch-PC kernel: ahci 0000:00:1f.2: version 3.0
mai 14 14:15:09 Arch-PC kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1b impl SATA mode
mai 14 14:15:09 Arch-PC kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst
mai 14 14:15:09 Arch-PC kernel: scsi host0: ahci
mai 14 14:15:09 Arch-PC kernel: scsi host1: ahci
mai 14 14:15:09 Arch-PC kernel: scsi host2: ahci
mai 14 14:15:09 Arch-PC kernel: scsi host3: ahci
mai 14 14:15:09 Arch-PC kernel: scsi host4: ahci
mai 14 14:15:09 Arch-PC kernel: scsi host5: ahci
mai 14 14:15:09 Arch-PC kernel: ata1: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a100 irq 27
mai 14 14:15:09 Arch-PC kernel: ata2: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a180 irq 27
mai 14 14:15:09 Arch-PC kernel: ata3: DUMMY
mai 14 14:15:09 Arch-PC kernel: ata4: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a280 irq 27
mai 14 14:15:09 Arch-PC kernel: ata5: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a300 irq 27
mai 14 14:15:09 Arch-PC kernel: ata6: DUMMY
mai 14 14:15:09 Arch-PC kernel: usbcore: registered new interface driver usbserial_generic
mai 14 14:15:09 Arch-PC kernel: usbserial: USB Serial support registered for generic
mai 14 14:15:09 Arch-PC kernel: rtc_cmos 00:02: RTC can wake from S4
mai 14 14:15:09 Arch-PC kernel: rtc_cmos 00:02: registered as rtc0
mai 14 14:15:09 Arch-PC kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
mai 14 14:15:09 Arch-PC kernel: intel_pstate: Intel P-state driver initializing
mai 14 14:15:09 Arch-PC kernel: ledtrig-cpu: registered to indicate activity on CPUs
mai 14 14:15:09 Arch-PC kernel: drop_monitor: Initializing network drop monitor service
mai 14 14:15:09 Arch-PC kernel: NET: Registered protocol family 10
mai 14 14:15:09 Arch-PC kernel: Segment Routing with IPv6
mai 14 14:15:09 Arch-PC kernel: NET: Registered protocol family 17
mai 14 14:15:09 Arch-PC kernel: RAS: Correctable Errors collector initialized.
mai 14 14:15:09 Arch-PC kernel: microcode: sig=0x306c3, pf=0x2, revision=0x27
mai 14 14:15:09 Arch-PC kernel: microcode: Microcode Update Driver: v2.2.
mai 14 14:15:09 Arch-PC kernel: IPI shorthand broadcast: enabled
mai 14 14:15:09 Arch-PC kernel: sched_clock: Marking stable (513828446, 194506)->(519703204, -5680252)
mai 14 14:15:09 Arch-PC kernel: registered taskstats version 1
mai 14 14:15:09 Arch-PC kernel: Loading compiled-in X.509 certificates
mai 14 14:15:09 Arch-PC kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 8efc0745a0f4f1a15f5910b82807b1e1a48255ac'
mai 14 14:15:09 Arch-PC kernel: zswap: loaded using pool lzo/zbud
mai 14 14:15:09 Arch-PC kernel: Key type ._fscrypt registered
mai 14 14:15:09 Arch-PC kernel: Key type .fscrypt registered
mai 14 14:15:09 Arch-PC kernel: Key type fscrypt-provisioning registered
mai 14 14:15:09 Arch-PC kernel: Key type big_key registered
mai 14 14:15:09 Arch-PC kernel: PM: Magic number: 4:568:289
mai 14 14:15:09 Arch-PC kernel: tty tty22: hash matches
mai 14 14:15:09 Arch-PC kernel: rtc_cmos 00:02: setting system clock to 2020-05-14T17:15:02 UTC (1589476502)
mai 14 14:15:09 Arch-PC kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
mai 14 14:15:09 Arch-PC kernel: ata1.00: HPA detected: current 1953523055, native 1953525168
mai 14 14:15:09 Arch-PC kernel: ata1.00: ATA-9: WDC WD10EZEX-00BN5A0, 01.01A01, max UDMA/133
mai 14 14:15:09 Arch-PC kernel: ata1.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 32), AA
mai 14 14:15:09 Arch-PC kernel: ata1.00: configured for UDMA/133
mai 14 14:15:09 Arch-PC kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD10EZEX-00B 1A01 PQ: 0 ANSI: 5
mai 14 14:15:09 Arch-PC kernel: sd 0:0:0:0: [sda] 1953523055 512-byte logical blocks: (1.00 TB/932 GiB)
mai 14 14:15:09 Arch-PC kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
mai 14 14:15:09 Arch-PC kernel: sd 0:0:0:0: [sda] Write Protect is off
mai 14 14:15:09 Arch-PC kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
mai 14 14:15:09 Arch-PC kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mai 14 14:15:09 Arch-PC kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
mai 14 14:15:09 Arch-PC kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
mai 14 14:15:09 Arch-PC kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
mai 14 14:15:09 Arch-PC kernel: ata4.00: ATA-9: ST2000DM006-2DM164, CC26, max UDMA/133
mai 14 14:15:09 Arch-PC kernel: ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
mai 14 14:15:09 Arch-PC kernel: ata2.00: HPA detected: current 1953523055, native 1953525168
mai 14 14:15:09 Arch-PC kernel: ata2.00: ATA-8: ST31000524AS, JC45, max UDMA/133
mai 14 14:15:09 Arch-PC kernel: ata2.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 32)
mai 14 14:15:09 Arch-PC kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
mai 14 14:15:09 Arch-PC kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
mai 14 14:15:09 Arch-PC kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
mai 14 14:15:09 Arch-PC kernel: ata5.00: ATAPI: HL-DT-ST BD-RE WH14NS40, 1.03, max UDMA/100
mai 14 14:15:09 Arch-PC kernel: ata4.00: configured for UDMA/133
mai 14 14:15:09 Arch-PC kernel: ata2.00: configured for UDMA/133
mai 14 14:15:09 Arch-PC kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
mai 14 14:15:09 Arch-PC kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
mai 14 14:15:09 Arch-PC kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
mai 14 14:15:09 Arch-PC kernel: scsi 1:0:0:0: Direct-Access ATA ST31000524AS JC45 PQ: 0 ANSI: 5
mai 14 14:15:09 Arch-PC kernel: sd 1:0:0:0: [sdb] 1953523055 512-byte logical blocks: (1.00 TB/932 GiB)
mai 14 14:15:09 Arch-PC kernel: sd 1:0:0:0: [sdb] Write Protect is off
mai 14 14:15:09 Arch-PC kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
mai 14 14:15:09 Arch-PC kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mai 14 14:15:09 Arch-PC kernel: scsi 3:0:0:0: Direct-Access ATA ST2000DM006-2DM1 CC26 PQ: 0 ANSI: 5
mai 14 14:15:09 Arch-PC kernel: ata5.00: configured for UDMA/100
mai 14 14:15:09 Arch-PC kernel: sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
mai 14 14:15:09 Arch-PC kernel: sd 3:0:0:0: [sdc] 4096-byte physical blocks
mai 14 14:15:09 Arch-PC kernel: sd 3:0:0:0: [sdc] Write Protect is off
mai 14 14:15:09 Arch-PC kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
mai 14 14:15:09 Arch-PC kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mai 14 14:15:09 Arch-PC kernel: sdc: sdc1
mai 14 14:15:09 Arch-PC kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
mai 14 14:15:09 Arch-PC kernel: scsi 4:0:0:0: CD-ROM HL-DT-ST BD-RE WH14NS40 1.03 PQ: 0 ANSI: 5
mai 14 14:15:09 Arch-PC kernel: sdb: sdb1
mai 14 14:15:09 Arch-PC kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
mai 14 14:15:09 Arch-PC kernel: sda: sda1 sda2 sda3 sda4
mai 14 14:15:09 Arch-PC kernel: sd 0:0:0:0: [sda] Attached SCSI disk
mai 14 14:15:09 Arch-PC kernel: Freeing unused decrypted memory: 2040K
mai 14 14:15:09 Arch-PC kernel: Freeing unused kernel image (initmem) memory: 1608K
mai 14 14:15:09 Arch-PC kernel: Write protecting the kernel read-only data: 20480k
mai 14 14:15:09 Arch-PC kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
mai 14 14:15:09 Arch-PC kernel: Freeing unused kernel image (rodata/data gap) memory: 1680K
mai 14 14:15:09 Arch-PC kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
mai 14 14:15:09 Arch-PC kernel: x86/mm: Checking user space page tables
mai 14 14:15:09 Arch-PC kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
mai 14 14:15:09 Arch-PC kernel: Run /init as init process
mai 14 14:15:09 Arch-PC kernel: with arguments:
mai 14 14:15:09 Arch-PC kernel: /init
mai 14 14:15:09 Arch-PC kernel: with environment:
mai 14 14:15:09 Arch-PC kernel: HOME=/
mai 14 14:15:09 Arch-PC kernel: TERM=linux
mai 14 14:15:09 Arch-PC kernel: BOOT_IMAGE=/boot/vmlinuz-linux
mai 14 14:15:09 Arch-PC kernel: fbcon: Taking over console
mai 14 14:15:09 Arch-PC kernel: Console: switching to colour frame buffer device 240x67
mai 14 14:15:09 Arch-PC kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mai 14 14:15:09 Arch-PC kernel: ehci-pci: EHCI PCI platform driver
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1a.0: debug port 2
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7d1c000
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
mai 14 14:15:09 Arch-PC kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
mai 14 14:15:09 Arch-PC kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 14:15:09 Arch-PC kernel: usb usb1: Product: EHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: usb usb1: Manufacturer: Linux 5.6.12-arch1-1 ehci_hcd
mai 14 14:15:09 Arch-PC kernel: usb usb1: SerialNumber: 0000:00:1a.0
mai 14 14:15:09 Arch-PC kernel: hub 1-0:1.0: USB hub found
mai 14 14:15:09 Arch-PC kernel: hub 1-0:1.0: 2 ports detected
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
mai 14 14:15:09 Arch-PC kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
mai 14 14:15:09 Arch-PC kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 14:15:09 Arch-PC kernel: usb usb2: Product: xHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: usb usb2: Manufacturer: Linux 5.6.12-arch1-1 xhci-hcd
mai 14 14:15:09 Arch-PC kernel: usb usb2: SerialNumber: 0000:00:14.0
mai 14 14:15:09 Arch-PC kernel: hub 2-0:1.0: USB hub found
mai 14 14:15:09 Arch-PC kernel: hub 2-0:1.0: 12 ports detected
mai 14 14:15:09 Arch-PC kernel: sr 4:0:0:0: [sr0] scsi3-mmc drive: 47x/94x writer dvd-ram cd/rw xa/form2 cdda tray
mai 14 14:15:09 Arch-PC kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 3
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1d.0: debug port 2
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
mai 14 14:15:09 Arch-PC kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
mai 14 14:15:09 Arch-PC kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.06
mai 14 14:15:09 Arch-PC kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 14:15:09 Arch-PC kernel: usb usb4: Product: xHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: usb usb4: Manufacturer: Linux 5.6.12-arch1-1 xhci-hcd
mai 14 14:15:09 Arch-PC kernel: usb usb4: SerialNumber: 0000:00:14.0
mai 14 14:15:09 Arch-PC kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
mai 14 14:15:09 Arch-PC kernel: hub 4-0:1.0: USB hub found
mai 14 14:15:09 Arch-PC kernel: hub 4-0:1.0: 6 ports detected
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7d1b000
mai 14 14:15:09 Arch-PC kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
mai 14 14:15:09 Arch-PC kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
mai 14 14:15:09 Arch-PC kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
mai 14 14:15:09 Arch-PC kernel: usb usb3: Product: EHCI Host Controller
mai 14 14:15:09 Arch-PC kernel: usb usb3: Manufacturer: Linux 5.6.12-arch1-1 ehci_hcd
mai 14 14:15:09 Arch-PC kernel: usb usb3: SerialNumber: 0000:00:1d.0
mai 14 14:15:09 Arch-PC kernel: hub 3-0:1.0: USB hub found
mai 14 14:15:09 Arch-PC kernel: hub 3-0:1.0: 2 ports detected
mai 14 14:15:09 Arch-PC kernel: random: fast init done
mai 14 14:15:09 Arch-PC kernel: tsc: Refined TSC clocksource calibration: 2693.761 MHz
mai 14 14:15:09 Arch-PC kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x26d438c619d, max_idle_ns: 440795237946 ns
mai 14 14:15:09 Arch-PC kernel: clocksource: Switched to clocksource tsc
mai 14 14:15:09 Arch-PC kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
mai 14 14:15:09 Arch-PC kernel: usb 2-9: new low-speed USB device number 2 using xhci_hcd
mai 14 14:15:09 Arch-PC kernel: usb 3-1: new high-speed USB device number 2 using ehci-pci
mai 14 14:15:09 Arch-PC kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=8008, bcdDevice= 0.05
mai 14 14:15:09 Arch-PC kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
mai 14 14:15:09 Arch-PC kernel: hub 1-1:1.0: USB hub found
mai 14 14:15:09 Arch-PC kernel: hub 1-1:1.0: 6 ports detected
mai 14 14:15:09 Arch-PC kernel: usb 2-9: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=64.00
mai 14 14:15:09 Arch-PC kernel: usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
mai 14 14:15:09 Arch-PC kernel: usb 2-9: Product: USB Keyboard
mai 14 14:15:09 Arch-PC kernel: usb 2-9: Manufacturer: Logitech
mai 14 14:15:09 Arch-PC kernel: hid: raw HID events driver (C) Jiri Kosina
mai 14 14:15:09 Arch-PC kernel: usbcore: registered new interface driver usbhid
mai 14 14:15:09 Arch-PC kernel: usbhid: USB HID core driver
mai 14 14:15:09 Arch-PC kernel: usb 3-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.05
mai 14 14:15:09 Arch-PC kernel: usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
mai 14 14:15:09 Arch-PC kernel: hub 3-1:1.0: USB hub found
mai 14 14:15:09 Arch-PC kernel: hub 3-1:1.0: 6 ports detected
mai 14 14:15:09 Arch-PC kernel: input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/0003:046D:C31C.0001/input/input2
mai 14 14:15:09 Arch-PC kernel: hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-0000:00:14.0-9/input0
mai 14 14:15:09 Arch-PC kernel: input: Logitech USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/input/input3
mai 14 14:15:09 Arch-PC kernel: usb 2-10: new low-speed USB device number 3 using xhci_hcd
mai 14 14:15:09 Arch-PC kernel: input: Logitech USB Keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/input/input4
mai 14 14:15:09 Arch-PC kernel: hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-0000:00:14.0-9/input1
mai 14 14:15:09 Arch-PC kernel: usb 2-10: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00
mai 14 14:15:09 Arch-PC kernel: usb 2-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
mai 14 14:15:09 Arch-PC kernel: usb 2-10: Product: USB Optical Mouse
mai 14 14:15:09 Arch-PC kernel: usb 2-10: Manufacturer: Logitech
mai 14 14:15:09 Arch-PC kernel: input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/0003:046D:C077.0003/input/input5
mai 14 14:15:09 Arch-PC kernel: hid-generic 0003:046D:C077.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-10/input0
mai 14 14:15:09 Arch-PC kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
mai 14 14:15:09 Arch-PC kernel: random: crng init done
mai 14 14:15:09 Arch-PC systemd[1]: systemd 245.5-2-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
mai 14 14:15:09 Arch-PC systemd[1]: Detected architecture x86-64.
mai 14 14:15:09 Arch-PC systemd[1]: Set hostname to <Arch-PC>.
mai 14 14:15:09 Arch-PC systemd[1]: Created slice system-getty.slice.
mai 14 14:15:09 Arch-PC systemd[1]: Created slice system-modprobe.slice.
mai 14 14:15:09 Arch-PC systemd[1]: Created slice User and Session Slice.
mai 14 14:15:09 Arch-PC systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
mai 14 14:15:09 Arch-PC systemd[1]: Started Forward Password Requests to Wall Directory Watch.
mai 14 14:15:09 Arch-PC systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
mai 14 14:15:09 Arch-PC systemd[1]: Reached target Local Encrypted Volumes.
mai 14 14:15:09 Arch-PC systemd[1]: Reached target Login Prompts.
mai 14 14:15:09 Arch-PC systemd[1]: Reached target Paths.
mai 14 14:15:09 Arch-PC systemd[1]: Reached target Remote File Systems.
mai 14 14:15:09 Arch-PC systemd[1]: Reached target Slices.
mai 14 14:15:09 Arch-PC systemd[1]: Reached target Swap.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on Device-mapper event daemon FIFOs.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on LVM2 metadata daemon socket.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on LVM2 poll daemon socket.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on Process Core Dump Socket.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on initctl Compatibility Named Pipe.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on Journal Audit Socket.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on Journal Socket (/dev/log).
mai 14 14:15:09 Arch-PC systemd[1]: Listening on Journal Socket.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on udev Control Socket.
mai 14 14:15:09 Arch-PC systemd[1]: Listening on udev Kernel Socket.
mai 14 14:15:09 Arch-PC systemd[1]: Mounting Huge Pages File System...
mai 14 14:15:09 Arch-PC systemd[1]: Mounting POSIX Message Queue File System...
mai 14 14:15:09 Arch-PC systemd[1]: Mounting Kernel Debug File System...
mai 14 14:15:09 Arch-PC systemd[1]: Mounting Kernel Trace File System...
mai 14 14:15:09 Arch-PC systemd[1]: Mounting Temporary Directory (/tmp)...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Create list of static device nodes for the current kernel...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Load Kernel Module drm...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Set Up Additional Binary Formats...
mai 14 14:15:09 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:15:09 Arch-PC systemd[1]: Starting Journal Service...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Load Kernel Modules...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Remount Root and Kernel File Systems...
mai 14 14:15:09 Arch-PC systemd[1]: Starting udev Coldplug all Devices...
mai 14 14:15:09 Arch-PC systemd[1]: Mounted Huge Pages File System.
mai 14 14:15:09 Arch-PC systemd[1]: Mounted POSIX Message Queue File System.
mai 14 14:15:09 Arch-PC systemd[1]: Mounted Kernel Debug File System.
mai 14 14:15:09 Arch-PC systemd[1]: Mounted Kernel Trace File System.
mai 14 14:15:09 Arch-PC kernel: Linux agpgart interface v0.103
mai 14 14:15:09 Arch-PC systemd[1]: Mounted Temporary Directory (/tmp).
mai 14 14:15:09 Arch-PC systemd[1]: Finished Create list of static device nodes for the current kernel.
mai 14 14:15:09 Arch-PC systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 270 (systemd-binfmt)
mai 14 14:15:09 Arch-PC systemd[1]: Mounting Arbitrary Executable File Formats File System...
mai 14 14:15:09 Arch-PC systemd[1]: Mounted Arbitrary Executable File Formats File System.
mai 14 14:15:09 Arch-PC kernel: EXT4-fs (sda3): re-mounted. Opts: (null)
mai 14 14:15:09 Arch-PC systemd[1]: Finished Remount Root and Kernel File Systems.
mai 14 14:15:09 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:15:09 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:15:09 Arch-PC systemd[1]: Starting Load/Save Random Seed...
mai 14 14:15:09 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:15:09 Arch-PC systemd[1]: Starting Create Static Device Nodes in /dev...
mai 14 14:15:09 Arch-PC systemd[1]: Finished Set Up Additional Binary Formats.
mai 14 14:15:09 Arch-PC systemd[1]: Finished udev Coldplug all Devices.
mai 14 14:15:09 Arch-PC systemd[1]: Started LVM2 metadata daemon.
mai 14 14:15:09 Arch-PC systemd[1]: modprobe@drm.service: Succeeded.
mai 14 14:15:09 Arch-PC systemd[1]: Finished Load Kernel Module drm.
mai 14 14:15:09 Arch-PC kernel: vhba: loading out-of-tree module taints kernel.
mai 14 14:15:09 Arch-PC kernel: vhba: module verification failed: signature and/or required key missing - tainting kernel
mai 14 14:15:09 Arch-PC kernel: scsi host6: vhba
mai 14 14:15:09 Arch-PC systemd[1]: Finished Load/Save Random Seed.
mai 14 14:15:09 Arch-PC systemd-journald[271]: Journal started
mai 14 14:15:09 Arch-PC systemd-journald[271]: Runtime Journal (/run/log/journal/4bac3062eca442b1b88ff64657a50777) is 8.0M, max 393.2M, 385.2M free.
mai 14 14:15:09 Arch-PC systemd-modules-load[272]: Inserted module 'crypto_user'
mai 14 14:15:09 Arch-PC systemd-modules-load[272]: Inserted module 'vhba'
mai 14 14:15:09 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:09 Arch-PC systemd[1]: Started Journal Service.
mai 14 14:15:09 Arch-PC kernel: audit: type=1130 audit(1589476509.435:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:09 Arch-PC systemd[1]: Starting Flush Journal to Persistent Storage...
mai 14 14:15:09 Arch-PC systemd-journald[271]: Time spent on flushing to /var/log/journal/4bac3062eca442b1b88ff64657a50777 is 342.265ms for 783 entries.
mai 14 14:15:09 Arch-PC systemd-journald[271]: System Journal (/var/log/journal/4bac3062eca442b1b88ff64657a50777) is 4.0G, max 4.0G, 0B free.
mai 14 14:15:12 Arch-PC kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
mai 14 14:15:12 Arch-PC kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
mai 14 14:15:12 Arch-PC kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0
mai 14 14:15:12 Arch-PC kernel: sr 4:0:0:0: Attached scsi generic sg3 type 5
mai 14 14:15:12 Arch-PC kernel: vboxdrv: Found 2 processor cores
mai 14 14:15:12 Arch-PC kernel: vboxdrv: TSC mode is Invariant, tentative frequency 2693757872 Hz
mai 14 14:15:12 Arch-PC kernel: vboxdrv: Successfully loaded version 6.1.6 (interface 0x002d0001)
mai 14 14:15:12 Arch-PC kernel: VBoxNetAdp: Successfully started.
mai 14 14:15:12 Arch-PC kernel: VBoxNetFlt: Successfully started.
mai 14 14:15:12 Arch-PC kernel: audit: type=1130 audit(1589476509.795:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:12 Arch-PC kernel: audit: type=1130 audit(1589476510.029:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:12 Arch-PC kernel: audit: type=1130 audit(1589476510.052:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:12 Arch-PC kernel: audit: type=1334 audit(1589476510.052:6): prog-id=5 op=LOAD
mai 14 14:15:12 Arch-PC kernel: audit: type=1334 audit(1589476510.052:7): prog-id=6 op=LOAD
mai 14 14:15:09 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:10 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:10 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:10 Arch-PC audit: AUDIT1334 prog-id=5 op=LOAD
mai 14 14:15:10 Arch-PC audit: AUDIT1334 prog-id=6 op=LOAD
mai 14 14:15:09 Arch-PC systemd-modules-load[272]: Inserted module 'sg'
mai 14 14:15:09 Arch-PC systemd-modules-load[272]: Inserted module 'vboxdrv'
mai 14 14:15:09 Arch-PC systemd-modules-load[272]: Inserted module 'vboxnetadp'
mai 14 14:15:09 Arch-PC systemd-modules-load[272]: Inserted module 'vboxnetflt'
mai 14 14:15:09 Arch-PC systemd[1]: Finished Load Kernel Modules.
mai 14 14:15:12 Arch-PC kernel: audit: type=1130 audit(1589476512.232:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:12 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:09 Arch-PC systemd[1]: Condition check resulted in FUSE Control File System being skipped.
mai 14 14:15:09 Arch-PC systemd[1]: Mounting Kernel Configuration File System...
mai 14 14:15:09 Arch-PC systemd[1]: Starting Apply Kernel Variables...
mai 14 14:15:09 Arch-PC systemd[1]: Mounted Kernel Configuration File System.
mai 14 14:15:10 Arch-PC systemd[1]: Finished Create Static Device Nodes in /dev.
mai 14 14:15:10 Arch-PC systemd-sysctl[290]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
mai 14 14:15:10 Arch-PC systemd-sysctl[290]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
mai 14 14:15:10 Arch-PC systemd-sysctl[290]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
mai 14 14:15:10 Arch-PC systemd-sysctl[290]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists).
mai 14 14:15:10 Arch-PC systemd-sysctl[290]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
mai 14 14:15:10 Arch-PC systemd-sysctl[290]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
mai 14 14:15:10 Arch-PC systemd[1]: Finished Apply Kernel Variables.
mai 14 14:15:10 Arch-PC systemd[1]: Starting udev Kernel Device Manager...
mai 14 14:15:12 Arch-PC systemd[1]: Finished Flush Journal to Persistent Storage.
mai 14 14:15:12 Arch-PC systemd[1]: Started udev Kernel Device Manager.
mai 14 14:15:12 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:12 Arch-PC kernel: audit: type=1130 audit(1589476512.635:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:12 Arch-PC kernel: i801_smbus 0000:00:1f.3: enabling device (0001 -> 0003)
mai 14 14:15:12 Arch-PC kernel: i801_smbus 0000:00:1f.3: SPD Write Disable is set
mai 14 14:15:12 Arch-PC kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
mai 14 14:15:12 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20200110/utaddress-204)
mai 14 14:15:12 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 14:15:12 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200110/utaddress-204)
mai 14 14:15:12 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 14:15:12 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200110/utaddress-204)
mai 14 14:15:12 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200110/utaddress-204)
mai 14 14:15:12 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 14:15:12 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200110/utaddress-204)
mai 14 14:15:12 Arch-PC kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200110/utaddress-204)
mai 14 14:15:12 Arch-PC kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mai 14 14:15:12 Arch-PC kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
mai 14 14:15:13 Arch-PC kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
mai 14 14:15:13 Arch-PC systemd-udevd[307]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
mai 14 14:15:13 Arch-PC kernel: RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
mai 14 14:15:13 Arch-PC kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
mai 14 14:15:13 Arch-PC kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
mai 14 14:15:13 Arch-PC kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
mai 14 14:15:13 Arch-PC kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
mai 14 14:15:13 Arch-PC systemd[1]: Found device ST31000524AS SEAGATE.
mai 14 14:15:13 Arch-PC systemd[1]: Found device ST2000DM006-2DM164 2TB.
mai 14 14:15:13 Arch-PC systemd[1]: Found device WDC_WD10EZEX-00BN5A0 WD.
mai 14 14:15:13 Arch-PC kernel: iTCO_vendor_support: vendor-support=0
mai 14 14:15:13 Arch-PC kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
mai 14 14:15:13 Arch-PC kernel: iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
mai 14 14:15:13 Arch-PC kernel: r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
mai 14 14:15:13 Arch-PC kernel: libphy: r8169: probed
mai 14 14:15:13 Arch-PC kernel: r8169 0000:04:00.0 eth0: RTL8168evl/8111evl, fc:aa:14:fc:4b:1b, XID 2c9, IRQ 30
mai 14 14:15:13 Arch-PC kernel: r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
mai 14 14:15:13 Arch-PC kernel: intel-spi intel-spi: mx25l6405d (8192 Kbytes)
mai 14 14:15:13 Arch-PC systemd-udevd[305]: Using default interface naming scheme 'v245'.
mai 14 14:15:13 Arch-PC systemd-udevd[305]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
mai 14 14:15:13 Arch-PC kernel: r8169 0000:04:00.0 enp4s0: renamed from eth0
mai 14 14:15:13 Arch-PC systemd-udevd[308]: Using default interface naming scheme 'v245'.
mai 14 14:15:13 Arch-PC mtp-probe[347]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-10"
mai 14 14:15:13 Arch-PC kernel: Creating 1 MTD partitions on "intel-spi":
mai 14 14:15:13 Arch-PC kernel: 0x000000000000-0x000000800000 : "BIOS"
mai 14 14:15:13 Arch-PC mtp-probe[348]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-9"
mai 14 14:15:13 Arch-PC mtp-probe[348]: bus: 2, device: 2 was not an MTP device
mai 14 14:15:13 Arch-PC mtp-probe[347]: bus: 2, device: 3 was not an MTP device
mai 14 14:15:13 Arch-PC kernel: cryptd: max_cpu_qlen set to 1000
mai 14 14:15:14 Arch-PC kernel: checking generic (e0000000 7f0000) vs hw (f7800000 400000)
mai 14 14:15:14 Arch-PC kernel: checking generic (e0000000 7f0000) vs hw (e0000000 10000000)
mai 14 14:15:14 Arch-PC kernel: fb0: switching to inteldrmfb from VESA VGA
mai 14 14:15:14 Arch-PC kernel: Console: switching to colour dummy device 80x25
mai 14 14:15:14 Arch-PC kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
mai 14 14:15:14 Arch-PC kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
mai 14 14:15:14 Arch-PC kernel: [drm] Driver supports precise vblank timestamp query.
mai 14 14:15:14 Arch-PC kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
mai 14 14:15:14 Arch-PC kernel: [drm] Initialized i915 1.6.0 20200114 for 0000:00:02.0 on minor 0
mai 14 14:15:14 Arch-PC kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
mai 14 14:15:14 Arch-PC kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
mai 14 14:15:14 Arch-PC kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
mai 14 14:15:14 Arch-PC systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
mai 14 14:15:14 Arch-PC systemd[1]: Reached target Local File Systems (Pre).
mai 14 14:15:14 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:14 Arch-PC kernel: audit: type=1130 audit(1589476514.502:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: mono: mono_out=0x0
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: dig-out=0x11/0x0
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: inputs:
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: Rear Mic=0x18
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: Front Mic=0x19
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: Line=0x1a
mai 14 14:15:14 Arch-PC kernel: snd_hda_codec_realtek hdaudioC1D2: CD=0x1c
mai 14 14:15:14 Arch-PC systemd[1]: Mounting /mnt/2TB...
mai 14 14:15:14 Arch-PC kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card1/input8
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input10
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card1/input11
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card1/input12
mai 14 14:15:14 Arch-PC kernel: mousedev: PS/2 mouse device common for all mice
mai 14 14:15:14 Arch-PC kernel: fbcon: i915drmfb (fb0) is primary device
mai 14 14:15:14 Arch-PC systemd[1]: Mounting /mnt/SEAGATE...
mai 14 14:15:14 Arch-PC systemd[1]: mnt-WD.mount: Directory /mnt/WD to mount over is not empty, mounting anyway.
mai 14 14:15:14 Arch-PC systemd[1]: Mounting /mnt/WD...
mai 14 14:15:14 Arch-PC systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
mai 14 14:15:14 Arch-PC systemd[1]: Mounting Mount unit for b1freearchiver...
mai 14 14:15:14 Arch-PC systemd[1]: Mounting Mount unit for b1freearchiver...
mai 14 14:15:14 Arch-PC systemd[1]: Mounting Mount unit for boa, revision 196...
mai 14 14:15:14 Arch-PC systemd[1]: Mounting Mount unit for boa, revision 202...
mai 14 14:15:14 Arch-PC kernel: Console: switching to colour frame buffer device 240x67
mai 14 14:15:14 Arch-PC kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input13
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input14
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input15
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/sound/card0/input16
mai 14 14:15:14 Arch-PC kernel: input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.0/sound/card0/input17
mai 14 14:15:15 Arch-PC kernel: loop: module loaded
mai 14 14:15:15 Arch-PC kernel: fuse: init (API version 7.31)
mai 14 14:15:15 Arch-PC kernel: *** VALIDATE fuseblk ***
mai 14 14:15:15 Arch-PC kernel: *** VALIDATE fuse ***
mai 14 14:15:15 Arch-PC kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
mai 14 14:15:15 Arch-PC ntfs-3g[462]: Version 2017.3.23 external FUSE 29
mai 14 14:15:15 Arch-PC ntfs-3g[462]: Mounted /dev/sdc1 (Read-Write, label "2TB", NTFS 3.1)
mai 14 14:15:15 Arch-PC ntfs-3g[462]: Cmdline options: rw,nosuid,nodev
mai 14 14:15:15 Arch-PC ntfs-3g[462]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,fsname=/dev/sdc1,blkdev,blksize=4096
mai 14 14:15:15 Arch-PC ntfs-3g[462]: Ownership and permissions disabled, configuration type 7
mai 14 14:15:15 Arch-PC systemd[1]: Mounting Mount unit for core, revision 8935...
mai 14 14:15:15 Arch-PC systemd[1]: Mounting Mount unit for core, revision 9066...
mai 14 14:15:15 Arch-PC ntfs-3g[467]: Version 2017.3.23 external FUSE 29
mai 14 14:15:15 Arch-PC ntfs-3g[467]: Mounted /dev/sdb1 (Read-Write, label "SEAGATE", NTFS 3.1)
mai 14 14:15:15 Arch-PC ntfs-3g[467]: Cmdline options: rw,nosuid,nodev
mai 14 14:15:15 Arch-PC ntfs-3g[467]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096
mai 14 14:15:15 Arch-PC ntfs-3g[467]: Ownership and permissions disabled, configuration type 7
mai 14 14:15:16 Arch-PC systemd-udevd[311]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
mai 14 14:15:16 Arch-PC systemd-udevd[298]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for core18, revision 1705...
mai 14 14:15:16 Arch-PC kernel: intel_rapl_common: Found RAPL domain package
mai 14 14:15:16 Arch-PC kernel: intel_rapl_common: Found RAPL domain core
mai 14 14:15:16 Arch-PC kernel: intel_rapl_common: Found RAPL domain uncore
mai 14 14:15:16 Arch-PC kernel: intel_rapl_common: Found RAPL domain dram
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for core18, revision 1754...
mai 14 14:15:16 Arch-PC kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for gnome-3-26-1604, revision 97...
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for gnome-3-26-1604, revision 98...
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for gnome-3-28-1804, revision 116...
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1502...
mai 14 14:15:16 Arch-PC systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1506...
mai 14 14:15:17 Arch-PC systemd[1]: Mounting Mount unit for kde-frameworks-5, revision 27...
mai 14 14:15:17 Arch-PC systemd[1]: Mounting Mount unit for opendvdproducer, revision 60...
mai 14 14:15:17 Arch-PC systemd[1]: Mounted /mnt/2TB.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted /mnt/SEAGATE.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted /mnt/WD.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for b1freearchiver.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for b1freearchiver.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for boa, revision 196.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for boa, revision 202.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for core, revision 8935.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for core, revision 9066.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for core18, revision 1705.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for core18, revision 1754.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for gnome-3-26-1604, revision 97.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for gnome-3-26-1604, revision 98.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for gnome-3-28-1804, revision 116.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1502.
mai 14 14:15:17 Arch-PC systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1506.
mai 14 14:15:18 Arch-PC systemd[1]: Mounted Mount unit for kde-frameworks-5, revision 27.
mai 14 14:15:18 Arch-PC systemd[1]: Mounting FUSE Control File System...
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Mounted Mount unit for opendvdproducer, revision 60.
mai 14 14:15:18 Arch-PC systemd[1]: Reached target Local File Systems.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Starting Create Volatile Files and Directories...
mai 14 14:15:18 Arch-PC systemd[1]: Mounted FUSE Control File System.
mai 14 14:15:18 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:18 Arch-PC systemd[1]: Finished Create Volatile Files and Directories.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:15:18 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:15:18 Arch-PC kernel: audit: type=1130 audit(1589476518.975:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:18 Arch-PC systemd[1]: Starting Update UTMP about System Boot/Shutdown...
mai 14 14:15:18 Arch-PC audit[490]: SYSTEM_BOOT pid=490 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
mai 14 14:15:19 Arch-PC kernel: audit: type=1127 audit(1589476518.992:12): pid=490 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
mai 14 14:15:19 Arch-PC systemd[1]: Finished Update UTMP about System Boot/Shutdown.
mai 14 14:15:19 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:19 Arch-PC systemd[1]: Reached target System Initialization.
mai 14 14:15:19 Arch-PC systemd[1]: Started Daily atop restart.
mai 14 14:15:19 Arch-PC systemd[1]: Started Daily rotation of log files.
mai 14 14:15:19 Arch-PC systemd[1]: Started Daily man-db regeneration.
mai 14 14:15:19 Arch-PC kernel: audit: type=1130 audit(1589476519.019:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:19 Arch-PC systemd[1]: Started Monthly clean packages cache.
mai 14 14:15:19 Arch-PC systemd[1]: Started Daily verification of password and group files.
mai 14 14:15:19 Arch-PC systemd[1]: Started Daily Cleanup of Temporary Directories.
mai 14 14:15:19 Arch-PC systemd[1]: Reached target Timers.
mai 14 14:15:19 Arch-PC systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
mai 14 14:15:19 Arch-PC systemd[1]: Listening on D-Bus System Message Bus Socket.
mai 14 14:15:19 Arch-PC systemd[1]: Starting Socket activation for snappy daemon.
mai 14 14:15:19 Arch-PC systemd[1]: Listening on Socket activation for snappy daemon.
mai 14 14:15:19 Arch-PC systemd[1]: Reached target Sockets.
mai 14 14:15:19 Arch-PC systemd[1]: Reached target Basic System.
mai 14 14:15:19 Arch-PC systemd[1]: Condition check resulted in Save/Restore Sound Card State being skipped.
mai 14 14:15:19 Arch-PC systemd[1]: Condition check resulted in Manage Sound Card State (restore and store) being skipped.
mai 14 14:15:19 Arch-PC systemd[1]: Reached target Sound Card.
mai 14 14:15:19 Arch-PC systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
mai 14 14:15:19 Arch-PC systemd[1]: Starting CDEmu Daemon...
mai 14 14:15:19 Arch-PC systemd[1]: Started D-Bus System Message Bus.
mai 14 14:15:19 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:19 Arch-PC kernel: audit: type=1130 audit(1589476519.065:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:19 Arch-PC systemd[1]: Starting Network Manager...
mai 14 14:15:19 Arch-PC systemd[1]: Starting Initialize hardware monitoring sensors...
mai 14 14:15:19 Arch-PC avahi-daemon[492]: Found user 'avahi' (UID 978) and group 'avahi' (GID 978).
mai 14 14:15:20 Arch-PC kernel: it87: Found IT8620E chip at 0xa30, revision 4
mai 14 14:15:20 Arch-PC kernel: it87: Beeping is supported
mai 14 14:15:20 Arch-PC NetworkManager[495]: <info> [1589476520.4369] NetworkManager (version 1.24.0-1) is starting... (for the first time)
mai 14 14:15:20 Arch-PC NetworkManager[495]: <info> [1589476520.4435] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
mai 14 14:15:20 Arch-PC systemd[1]: Condition check resulted in SSH Key Generation being skipped.
mai 14 14:15:20 Arch-PC audit: AUDIT1334 prog-id=7 op=LOAD
mai 14 14:15:20 Arch-PC kernel: audit: type=1334 audit(1589476520.495:15): prog-id=7 op=LOAD
mai 14 14:15:20 Arch-PC kernel: audit: type=1334 audit(1589476520.495:16): prog-id=8 op=LOAD
mai 14 14:15:20 Arch-PC audit: AUDIT1334 prog-id=8 op=LOAD
mai 14 14:15:20 Arch-PC systemd[1]: Starting Login Service...
mai 14 14:15:20 Arch-PC avahi-daemon[492]: Successfully dropped root privileges.
mai 14 14:15:20 Arch-PC avahi-daemon[492]: avahi-daemon 0.8 starting up.
mai 14 14:15:20 Arch-PC systemd[1]: Finished Initialize hardware monitoring sensors.
mai 14 14:15:20 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lm_sensors comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:20 Arch-PC kernel: audit: type=1130 audit(1589476520.599:17): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lm_sensors comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:20 Arch-PC systemd-logind[499]: New seat seat0.
mai 14 14:15:20 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event1 (Power Button)
mai 14 14:15:21 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event0 (Power Button)
mai 14 14:15:21 Arch-PC systemd[1]: Started Network Manager.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Reached target Network.
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.092:18): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC NetworkManager[495]: <info> [1589476521.0990] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
mai 14 14:15:21 Arch-PC systemd[1]: Starting Network Manager Wait Online...
mai 14 14:15:21 Arch-PC kernel: scsi 6:0:1:0: CD-ROM CDEmu CD-ROM 1.0 PQ: 0 ANSI: 0
mai 14 14:15:21 Arch-PC kernel: sr 6:0:1:0: [sr1] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
mai 14 14:15:21 Arch-PC kernel: sr 6:0:1:0: Attached scsi CD-ROM sr1
mai 14 14:15:21 Arch-PC kernel: sr 6:0:1:0: Attached scsi generic sg4 type 5
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Successfully called chroot().
mai 14 14:15:21 Arch-PC NetworkManager[495]: <info> [1589476521.1169] manager[0x5617dce44080]: monitoring kernel firmware directory '/lib/firmware'.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Successfully dropped remaining capabilities.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: No service file found in /etc/avahi/services.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emby-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.135:19): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emby-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Started Emby brings together your videos, music, photos, and live television..
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: New relevant interface lo.IPv6 for mDNS.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: New relevant interface lo.IPv4 for mDNS.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Network interface enumeration completed.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Registering new address record for ::1 on lo.*.
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Registering new address record for 127.0.0.1 on lo.IPv4.
mai 14 14:15:21 Arch-PC systemd[1]: Started LimboMedia.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=limbomedia comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.135:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=limbomedia comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Started OpenSSH Daemon.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.139:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Starting Subsonic...
mai 14 14:15:21 Arch-PC systemd[1]: Starting Permit User Sessions...
mai 14 14:15:21 Arch-PC systemd[1]: Started Avahi mDNS/DNS-SD Stack.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.145:22): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Started CDEmu Daemon.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cdemu-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.149:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cdemu-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event2 (Logitech USB Keyboard)
mai 14 14:15:21 Arch-PC systemd-logind[499]: Watching system buttons on /dev/input/event4 (Logitech USB Keyboard System Control)
mai 14 14:15:21 Arch-PC systemd[1]: Finished Permit User Sessions.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC kernel: audit: type=1130 audit(1589476521.195:24): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Starting GNOME Display Manager...
mai 14 14:15:21 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0 pid=495 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 14:15:21 Arch-PC subsonic.sh[513]: Started Subsonic [PID 521, /var/lib/subsonic/subsonic_sh.log]
mai 14 14:15:21 Arch-PC systemd[1]: Started Subsonic.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=subsonic comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC systemd[1]: Started Login Service.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC audit: AUDIT1334 prog-id=9 op=LOAD
mai 14 14:15:21 Arch-PC audit: AUDIT1334 prog-id=10 op=LOAD
mai 14 14:15:21 Arch-PC systemd[1]: Starting Hostname Service...
mai 14 14:15:21 Arch-PC sshd[512]: Server listening on 0.0.0.0 port 22.
mai 14 14:15:21 Arch-PC sshd[512]: Server listening on :: port 22.
mai 14 14:15:21 Arch-PC systemd[1]: Started GNOME Display Manager.
mai 14 14:15:21 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:21 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.7' (uid=0 pid=517 comm="/usr/bin/gdm ")
mai 14 14:15:21 Arch-PC avahi-daemon[492]: Server startup complete. Host name is Arch-PC.local. Local service cookie is 2177195939.
mai 14 14:15:22 Arch-PC systemd[1]: Reached target User and Group Name Lookups.
mai 14 14:15:22 Arch-PC systemd[1]: Starting Accounts Service...
mai 14 14:15:22 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.8' (uid=0 pid=528 comm="/usr/lib/accounts-daemon ")
mai 14 14:15:22 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.hostname1'
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.4629] hostname: hostname: using hostnamed
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.4630] hostname: hostname changed from (none) to "Arch-PC"
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.4772] dns-mgr[0x5617dce22220]: init: dns=default,systemd-resolved rc-manager=symlink
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.5386] manager[0x5617dce44080]: rfkill: Wi-Fi hardware radio set disabled
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.5387] manager[0x5617dce44080]: rfkill: WWAN hardware radio set disabled
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.6098] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-ovs.so)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.6457] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-wwan.so)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7080] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-team.so)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7155] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-wifi.so)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7162] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-adsl.so)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7433] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.24.0-1/libnm-device-plugin-bluetooth.so)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7444] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7446] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7447] manager: Networking is enabled by state file
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7586] dhcp-init: Using DHCP client 'internal'
mai 14 14:15:22 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.2' (uid=0 pid=495 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.7723] settings: Loaded settings plugin: keyfile (internal)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.8241] device (lo): carrier: link connected
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.8248] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.8269] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
mai 14 14:15:22 Arch-PC NetworkManager[495]: <info> [1589476522.8280] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
mai 14 14:15:22 Arch-PC kernel: RTL8211E Gigabit Ethernet r8169-400:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
mai 14 14:15:23 Arch-PC kernel: r8169 0000:04:00.0 enp4s0: Link is Down
mai 14 14:15:23 Arch-PC NetworkManager[495]: <info> [1589476523.1189] ovsdb: Não foi possível conectar: Arquivo ou diretório inexistente
mai 14 14:15:23 Arch-PC systemd[1]: Started Hostname Service.
mai 14 14:15:23 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:23 Arch-PC systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:15:23 Arch-PC systemd[1]: Starting Network Manager Script Dispatcher Service...
mai 14 14:15:23 Arch-PC systemd[1]: Starting Authorization Manager...
mai 14 14:15:23 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mai 14 14:15:23 Arch-PC systemd[1]: Started Network Manager Script Dispatcher Service.
mai 14 14:15:23 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:23 Arch-PC polkitd[535]: Started polkitd version 0.116
mai 14 14:15:23 Arch-PC polkitd[535]: Loading rules from directory /etc/polkit-1/rules.d
mai 14 14:15:23 Arch-PC polkitd[535]: Loading rules from directory /usr/share/polkit-1/rules.d
mai 14 14:15:23 Arch-PC polkitd[535]: Finished loading, compiling and executing 10 rules
mai 14 14:15:23 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
mai 14 14:15:23 Arch-PC systemd[1]: Started Authorization Manager.
mai 14 14:15:23 Arch-PC polkitd[535]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
mai 14 14:15:23 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:23 Arch-PC accounts-daemon[528]: started daemon version 0.6.55
mai 14 14:15:23 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.Accounts'
mai 14 14:15:23 Arch-PC systemd[1]: Started Accounts Service.
mai 14 14:15:23 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:23 Arch-PC audit[545]: USER_AUTH pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:15:23 Arch-PC audit[545]: USER_ACCT pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:15:23 Arch-PC audit[545]: CRED_ACQ pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0300] device (enp4s0): carrier: link connected
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0304] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
mai 14 14:15:26 Arch-PC kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0574] policy: auto-activating connection 'Internet' (ce90ca86-a34c-30a3-a2e6-db85b51a19a9)
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0587] device (enp4s0): Activation: starting connection 'Internet' (ce90ca86-a34c-30a3-a2e6-db85b51a19a9)
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0589] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0603] manager: NetworkManager state is now CONNECTING
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0611] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0620] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC avahi-daemon[492]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.50.
mai 14 14:15:26 Arch-PC avahi-daemon[492]: New relevant interface enp4s0.IPv4 for mDNS.
mai 14 14:15:26 Arch-PC avahi-daemon[492]: Registering new address record for 192.168.0.50 on enp4s0.IPv4.
mai 14 14:15:26 Arch-PC audit: AUDIT1334 prog-id=11 op=LOAD
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.0644] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC kernel: kauditd_printk_skb: 12 callbacks suppressed
mai 14 14:15:26 Arch-PC kernel: audit: type=1334 audit(1589476526.059:37): prog-id=11 op=LOAD
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.2271] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.2285] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.2304] manager: NetworkManager state is now CONNECTED_LOCAL
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.2343] manager: NetworkManager state is now CONNECTED_SITE
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.2355] policy: set 'Internet' (enp4s0) as default for IPv4 routing and DNS
mai 14 14:15:26 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.2' (uid=0 pid=495 comm="/usr/bin/NetworkManager --no-daemon ")
mai 14 14:15:26 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.3900] device (enp4s0): Activation: successful, device activated.
mai 14 14:15:26 Arch-PC NetworkManager[495]: <info> [1589476526.4081] manager: startup complete
mai 14 14:15:26 Arch-PC systemd[1]: Finished Network Manager Wait Online.
mai 14 14:15:26 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:26 Arch-PC systemd[1]: Created slice User Slice of UID 120.
mai 14 14:15:26 Arch-PC kernel: audit: type=1130 audit(1589476526.715:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:26 Arch-PC systemd[1]: Reached target Network is Online.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:15:26 Arch-PC systemd[1]: Starting Samba NMB Daemon...
mai 14 14:15:26 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/120...
mai 14 14:15:26 Arch-PC systemd-logind[499]: New session c1 of user gdm.
mai 14 14:15:26 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/120.
mai 14 14:15:26 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:26 Arch-PC kernel: audit: type=1130 audit(1589476526.789:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:26 Arch-PC systemd[1]: Starting User Manager for UID 120...
mai 14 14:15:27 Arch-PC NetworkManager[495]: <info> [1589476527.1271] manager: NetworkManager state is now CONNECTED_GLOBAL
mai 14 14:15:27 Arch-PC audit[565]: USER_ACCT pid=565 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:27 Arch-PC audit[565]: CRED_ACQ pid=565 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:15:27 Arch-PC systemd[565]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:15:27 Arch-PC kernel: audit: type=1101 audit(1589476527.232:40): pid=565 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:27 Arch-PC kernel: audit: type=1103 audit(1589476527.232:41): pid=565 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:15:27 Arch-PC kernel: audit: type=1006 audit(1589476527.232:42): pid=565 uid=0 old-auid=4294967295 auid=120 tty=(none) old-ses=4294967295 ses=1 res=1
mai 14 14:15:27 Arch-PC systemd[565]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
mai 14 14:15:27 Arch-PC audit[565]: USER_START pid=565 uid=0 auid=120 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:27 Arch-PC kernel: audit: type=1105 audit(1589476527.255:43): pid=565 uid=0 auid=120 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:27 Arch-PC audit: AUDIT1334 prog-id=12 op=LOAD
mai 14 14:15:27 Arch-PC audit: AUDIT1334 prog-id=12 op=UNLOAD
mai 14 14:15:27 Arch-PC kernel: audit: type=1334 audit(1589476527.275:44): prog-id=12 op=LOAD
mai 14 14:15:27 Arch-PC kernel: audit: type=1334 audit(1589476527.275:45): prog-id=12 op=UNLOAD
mai 14 14:15:27 Arch-PC avahi-daemon[492]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::feaa:14ff:fefc:4b1b.
mai 14 14:15:27 Arch-PC avahi-daemon[492]: New relevant interface enp4s0.IPv6 for mDNS.
mai 14 14:15:27 Arch-PC avahi-daemon[492]: Registering new address record for fe80::feaa:14ff:fefc:4b1b on enp4s0.*.
mai 14 14:15:29 Arch-PC systemd[1]: Started Samba NMB Daemon.
mai 14 14:15:29 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nmb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:29 Arch-PC kernel: audit: type=1130 audit(1589476529.105:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nmb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:29 Arch-PC systemd[1]: Starting Samba SMB Daemon...
mai 14 14:15:29 Arch-PC systemd[565]: Reached target Paths.
mai 14 14:15:29 Arch-PC systemd[565]: Reached target Timers.
mai 14 14:15:29 Arch-PC systemd[565]: Starting D-Bus User Message Bus Socket.
mai 14 14:15:29 Arch-PC systemd[565]: Listening on GnuPG network certificate management daemon.
mai 14 14:15:29 Arch-PC systemd[565]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:15:29 Arch-PC systemd[565]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:15:29 Arch-PC systemd[565]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:15:29 Arch-PC systemd[565]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 14:15:29 Arch-PC systemd[565]: Listening on p11-kit server.
mai 14 14:15:29 Arch-PC systemd[565]: Listening on Multimedia System.
mai 14 14:15:29 Arch-PC systemd[565]: Listening on Sound System.
mai 14 14:15:29 Arch-PC nmbd[563]: [2020/05/14 14:15:29.109495, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
mai 14 14:15:29 Arch-PC nmbd[563]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
mai 14 14:15:29 Arch-PC systemd[565]: Listening on D-Bus User Message Bus Socket.
mai 14 14:15:29 Arch-PC systemd[565]: Reached target Sockets.
mai 14 14:15:29 Arch-PC systemd[565]: Reached target Basic System.
mai 14 14:15:29 Arch-PC systemd[1]: Started User Manager for UID 120.
mai 14 14:15:29 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:29 Arch-PC systemd[565]: Starting Update XDG user dir configuration...
mai 14 14:15:29 Arch-PC systemd[1]: Started Session c1 of user gdm.
mai 14 14:15:29 Arch-PC audit[545]: USER_START pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:15:29 Arch-PC systemd[565]: xdg-user-dirs-update.service: Succeeded.
mai 14 14:15:29 Arch-PC systemd[565]: Finished Update XDG user dir configuration.
mai 14 14:15:29 Arch-PC systemd[565]: Reached target Main User Target.
mai 14 14:15:29 Arch-PC systemd[565]: Startup finished in 2.181s.
mai 14 14:15:30 Arch-PC systemd[565]: Started D-Bus User Message Bus.
mai 14 14:15:32 Arch-PC systemd[1]: Started Samba SMB Daemon.
mai 14 14:15:32 Arch-PC kernel: kauditd_printk_skb: 2 callbacks suppressed
mai 14 14:15:32 Arch-PC kernel: audit: type=1130 audit(1589476532.265:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:32 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:32 Arch-PC systemd[1]: Reached target Multi-User System.
mai 14 14:15:32 Arch-PC systemd[1]: Reached target Graphical Interface.
mai 14 14:15:32 Arch-PC systemd[1]: Startup finished in 3.072s (kernel) + 27.228s (userspace) = 30.301s.
mai 14 14:15:32 Arch-PC smbd[590]: [2020/05/14 14:15:32.270100, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
mai 14 14:15:32 Arch-PC smbd[590]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
mai 14 14:15:33 Arch-PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mai 14 14:15:33 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:33 Arch-PC kernel: audit: type=1131 audit(1589476533.975:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:37 Arch-PC java[511]: 2020-05-14 14:15:37,600 INFO lm.system - Starting LimboMedia Server ...
mai 14 14:15:37 Arch-PC java[511]: 2020-05-14 14:15:37,631 INFO lm.system - Execution location: /home/stalker/limbomedia
mai 14 14:15:37 Arch-PC java[511]: 2020-05-14 14:15:37,631 INFO lm.system - Datastore location: /home/stalker/limbomedia/data
mai 14 14:15:37 Arch-PC java[511]: 2020-05-14 14:15:37,631 INFO lm.system - Server config file: /home/stalker/limbomedia/data/limbomedia.cfg
mai 14 14:15:37 Arch-PC java[511]: 2020-05-14 14:15:37,634 INFO lm.system - Environment: Linux, 5.6.12-arch1-1, amd64 - Java 1.8.0_242, Oracle Corporation
mai 14 14:15:37 Arch-PC java[511]: 2020-05-14 14:15:37,670 INFO lm.system - Environment: Charset UTF-8, File Encoding UTF-8, Timezone America/Sao_Paulo - Fuso horário de Brasília
mai 14 14:15:38 Arch-PC java[511]: 2020-05-14 14:15:38,019 INFO lm.system - Starting module core -> The heart and soul of LimboMedia.
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:45 Arch-PC gnome-session[614]: gnome-session-binary[614]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:45 Arch-PC gnome-session-binary[614]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:45 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:46 Arch-PC gnome-session[614]: gnome-session-binary[614]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
mai 14 14:15:46 Arch-PC gnome-session-binary[614]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=614 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:15:49 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:15:50 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Successfully activated service 'org.a11y.Bus'
mai 14 14:15:51 Arch-PC org.gnome.Shell.desktop[683]: glamor: No eglstream capable devices found
mai 14 14:15:52 Arch-PC nmbd[563]: [2020/05/14 14:15:52.365456, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
mai 14 14:15:52 Arch-PC nmbd[563]: *****
mai 14 14:15:52 Arch-PC nmbd[563]:
mai 14 14:15:52 Arch-PC nmbd[563]: Samba name server ARCH-PC is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.50
mai 14 14:15:52 Arch-PC kernel: audit: type=1131 audit(1589476552.492:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:52 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:15:52 Arch-PC nmbd[563]:
mai 14 14:15:52 Arch-PC systemd[1]: systemd-hostnamed.service: Succeeded.
mai 14 14:15:52 Arch-PC nmbd[563]: *****
mai 14 14:15:52 Arch-PC audit: AUDIT1334 prog-id=10 op=UNLOAD
mai 14 14:15:52 Arch-PC audit: AUDIT1334 prog-id=9 op=UNLOAD
mai 14 14:15:52 Arch-PC kernel: audit: type=1334 audit(1589476552.622:52): prog-id=10 op=UNLOAD
mai 14 14:15:52 Arch-PC kernel: audit: type=1334 audit(1589476552.622:53): prog-id=9 op=UNLOAD
mai 14 14:15:52 Arch-PC java[511]: 2020-05-14 14:15:52,910 INFO lm.tools - Initialized tool: Magick. Executable: /usr/bin/magick. Version: ImageMagick 7.0.10-11 Q16 x86_64 2020-05-12 https://imagemagick.org.
mai 14 14:15:53 Arch-PC java[511]: 2020-05-14 14:15:53,309 INFO lm.tools - Initialized tool: FFprobe. Executable: /home/stalker/limbomedia/tools/ffmpeg/ffprobe. Version: ffprobe version 4.2.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2007-2019 the FFmpeg developers.
mai 14 14:15:53 Arch-PC emby-server[510]: Info Main: Application path: /usr/lib/emby-server/EmbyServer.dll
mai 14 14:15:53 Arch-PC java[511]: 2020-05-14 14:15:53,706 INFO lm.tools - Initialized tool: FFmpeg. Executable: /home/stalker/limbomedia/tools/ffmpeg/ffmpeg. Version: ffmpeg version 4.2.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2019 the FFmpeg developers.
mai 14 14:15:53 Arch-PC java[511]: 2020-05-14 14:15:53,747 INFO lm.system - CORE initialization started for LimboMedia Server Version 2.15. Instance name: LimboMedia
mai 14 14:15:53 Arch-PC java[511]: 2020-05-14 14:15:53,759 INFO lm.system - Checking/Initializing scheduler and registering jobs.
mai 14 14:15:53 Arch-PC java[511]: 2020-05-14 14:15:53,774 INFO lm.system - CORE initialization finished. Starting adapters now (http, dlna/upnp, api) ...
mai 14 14:15:54 Arch-PC java[511]: 2020-05-14 14:15:54,168 WARN lm.system.cert - Initializing certificate provider fallback. It's not secure and leads to browser warnings. If you use HTTPS you should really configure another real provider.
mai 14 14:15:54 Arch-PC java[511]: 2020-05-14 14:15:54,392 INFO lm.tools - Initialized tool: Shell (Bash). Executable: /usr/bin/bash. Version: GNU bash, versão 5.0.16(1)-release (x86_64-pc-linux-gnu).
mai 14 14:15:54 Arch-PC java[511]: 2020-05-14 14:15:54,916 INFO lm.system - Starting module web -> Webserver HTTP(S) for Webinterface, API, UPnP Mediastreaming.
mai 14 14:15:57 Arch-PC java[511]: 2020-05-14 14:15:57,290 INFO lm.web - Initialized local network security. Mapping anonymous requests (by UPnP/DLNA) to user 'LAN', restricted to netmasks 255.255.255.0(IPv4) and ffff:ffff:ffff:ff00::(IPv6).
mai 14 14:15:57 Arch-PC emby-server[510]: Info Main: Emby
mai 14 14:15:57 Arch-PC emby-server[510]: Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /var/lib/emby -ffdetect /usr/bin/ffdetect-emby -ffmpeg /usr/bin/ffmpeg-emby -ffprobe /usr/bin/ffprobe-emby -restartexitcode 3
mai 14 14:15:57 Arch-PC emby-server[510]: Operating system: Unix 5.6.12.1
mai 14 14:15:57 Arch-PC emby-server[510]: 64-Bit OS: True
mai 14 14:15:57 Arch-PC emby-server[510]: 64-Bit Process: True
mai 14 14:15:57 Arch-PC emby-server[510]: User Interactive: True
mai 14 14:15:57 Arch-PC emby-server[510]: Runtime: file:///usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Private.CoreLib.dll
mai 14 14:15:57 Arch-PC emby-server[510]: System.Environment.Version: 3.1.3
mai 14 14:15:57 Arch-PC emby-server[510]: Processor count: 2
mai 14 14:15:57 Arch-PC emby-server[510]: Program data path: /var/lib/emby
mai 14 14:15:57 Arch-PC emby-server[510]: Application directory: /usr/lib/emby-server
mai 14 14:15:58 Arch-PC emby-server[510]: Info App: Application version: 4.4.2.0
mai 14 14:15:58 Arch-PC emby-server[510]: Info App: Loading assemblies
mai 14 14:15:58 Arch-PC java[511]: 2020-05-14 14:15:58,826 INFO lm.web - Connector HTTP [http/1.1] started on *:8000 --> Visit http://192.168.0.50:8000
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,308 INFO lm.web - Connector HTTPS [ssl, http/1.1] started on *:8001 --> Visit https://192.168.0.50:8001
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,359 INFO lm.system - Starting module upnp -> UPnP/DLNA discovery and directory browsing.
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,692 INFO lm.system - ============================================================
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,693 INFO lm.system - Startup complete. Welcome to
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,693 INFO lm.system - __ _ __ __ ___ ___
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,693 INFO lm.system - / / (_)___ ___ / /_ ____ / |/ /__ ____/ (_)___ _
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,693 INFO lm.system - / / / / __ `__ \/ __ \/ __ \/ /|_/ / _ \/ __ / / __ `/
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,693 INFO lm.system - / /___/ / / / / / / /_/ / /_/ / / / / __/ /_/ / / /_/ /
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,693 INFO lm.system - /_____/_/_/ /_/ /_/_.___/\____/_/ /_/\___/\__,_/_/\__,_/
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,694 INFO lm.system - Version: 2.15 - Stamp: 202003032024
mai 14 14:15:59 Arch-PC java[511]: 2020-05-14 14:15:59,694 INFO lm.system - ============================================================
mai 14 14:15:59 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/Fanart.dll has version 1.0.7.0
mai 14 14:15:59 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/Fanart.dll has version 1.0.7.0
mai 14 14:15:59 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/StudioImages.dll has version 1.0.3.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/StudioImages.dll has version 1.0.3.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/DvdMounter.dll has version 1.0.0.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/DvdMounter.dll has version 1.0.0.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/OpenSubtitles.dll has version 1.0.26.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/OpenSubtitles.dll has version 1.0.26.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/Emby.PortMapper.dll has version 1.0.4.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/Emby.PortMapper.dll has version 1.0.4.0
mai 14 14:16:00 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/Emby.Server.CinemaMode.dll has version 1.0.31.0
mai 14 14:16:01 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/Emby.Server.CinemaMode.dll has version 1.0.31.0
mai 14 14:16:01 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/NfoMetadata.dll has version 1.0.29.0
mai 14 14:16:01 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/NfoMetadata.dll has version 1.0.29.0
mai 14 14:16:01 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/Emby.Webhooks.dll has version 1.0.11.0
mai 14 14:16:01 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/Emby.Webhooks.dll has version 1.0.11.0
mai 14 14:16:01 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/Emby.Dlna.dll has version 1.0.37.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/Emby.Dlna.dll has version 1.0.37.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/Tvdb.dll has version 1.0.31.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/Tvdb.dll has version 1.0.30.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/BlurayMounter.dll has version 1.0.0.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/BlurayMounter.dll has version 1.0.0.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/MovieDb.dll has version 1.3.4.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/MovieDb.dll has version 1.3.1.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/AudioDb.dll has version 1.0.10.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/AudioDb.dll has version 1.0.9.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/MusicBrainz.dll has version 1.0.13.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/MusicBrainz.dll has version 1.0.13.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /var/lib/emby/plugins/OMDb.dll has version 1.0.9.0
mai 14 14:16:02 Arch-PC emby-server[510]: Info App: File /usr/lib/emby-server/plugins/OMDb.dll has version 1.0.9.0
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Fanart, Version=1.0.7.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Fanart.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/StudioImages.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading DvdMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/DvdMounter.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading OpenSubtitles, Version=1.0.26.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OpenSubtitles.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.PortMapper, Version=1.0.4.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.PortMapper.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Server.CinemaMode, Version=1.0.31.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Server.CinemaMode.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading NfoMetadata, Version=1.0.29.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/NfoMetadata.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Webhooks, Version=1.0.11.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Webhooks.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Dlna, Version=1.0.37.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Dlna.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Tvdb, Version=1.0.31.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Tvdb.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading BlurayMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/BlurayMounter.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading MovieDb, Version=1.3.4.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MovieDb.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading AudioDb, Version=1.0.10.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/AudioDb.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading MusicBrainz, Version=1.0.13.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MusicBrainz.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading OMDb, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OMDb.dll
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Api, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Web, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading MediaBrowser.Model, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading MediaBrowser.Common, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading MediaBrowser.Controller, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Providers, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Photos, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Server.Implementations, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.LiveTV, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.ActivityLog, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Server.MediaEncoding, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.LocalMetadata, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Notifications, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Codecs.Dxva, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Codecs, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Server.Connect, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading Emby.Server.Sync, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:03 Arch-PC emby-server[510]: Info App: Loading EmbyServer, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null
mai 14 14:16:05 Arch-PC emby-server[510]: Info SqliteUserRepository: Sqlite version: 3.31.1
mai 14 14:16:05 Arch-PC emby-server[510]: Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-9.2.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_JSON1,ENABLE_RTREE,ENABLE_UNLOCK_NOTIFY,HAVE_ISNAN,MAX_EXPR_DEPTH=10000,MAX_VARIABLE_NUMBER=250000,SECURE_DELETE,TEMP_STORE=1,THREADSAFE=1
mai 14 14:16:05 Arch-PC emby-server[510]: Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is wal
mai 14 14:16:06 Arch-PC emby-server[510]: Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is wal
mai 14 14:16:06 Arch-PC emby-server[510]: Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is wal
mai 14 14:16:06 Arch-PC emby-server[510]: Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is wal
mai 14 14:16:06 Arch-PC emby-server[510]: Info App: Adding HttpListener prefix http://+:8096/
mai 14 14:16:07 Arch-PC emby-server[510]: Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is wal
mai 14 14:16:17 Arch-PC gnome-shell[650]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mai 14 14:16:17 Arch-PC gnome-shell[650]: Will monitor session c1
mai 14 14:16:17 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.23' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:17 Arch-PC audit: AUDIT1334 prog-id=13 op=LOAD
mai 14 14:16:17 Arch-PC kernel: audit: type=1334 audit(1589476577.639:54): prog-id=13 op=LOAD
mai 14 14:16:17 Arch-PC audit: AUDIT1334 prog-id=14 op=LOAD
mai 14 14:16:17 Arch-PC kernel: audit: type=1334 audit(1589476577.639:55): prog-id=14 op=LOAD
mai 14 14:16:17 Arch-PC systemd[1]: Starting Locale Service...
mai 14 14:16:17 Arch-PC gnome-shell[650]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:16:18 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.locale1'
mai 14 14:16:18 Arch-PC systemd[1]: Started Locale Service.
mai 14 14:16:18 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:18 Arch-PC kernel: audit: type=1130 audit(1589476578.169:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:20 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:20 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Successfully activated service 'ca.desrt.dconf'
mai 14 14:16:22 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.2' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:22 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
mai 14 14:16:23 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.23' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:23 Arch-PC audit: AUDIT1334 prog-id=15 op=LOAD
mai 14 14:16:23 Arch-PC kernel: audit: type=1334 audit(1589476583.059:57): prog-id=15 op=LOAD
mai 14 14:16:23 Arch-PC kernel: audit: type=1334 audit(1589476583.059:58): prog-id=16 op=LOAD
mai 14 14:16:23 Arch-PC audit: AUDIT1334 prog-id=16 op=LOAD
mai 14 14:16:23 Arch-PC systemd[1]: Starting Daemon for power management...
mai 14 14:16:23 Arch-PC systemd[565]: Starting Sound Service...
mai 14 14:16:23 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.UPower'
mai 14 14:16:23 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:23 Arch-PC systemd[1]: Started Daemon for power management.
mai 14 14:16:23 Arch-PC kernel: audit: type=1130 audit(1589476583.685:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:23 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=120 pid=779 comm="/usr/bin/pulseaudio --daemonize=no ")
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:16:23 Arch-PC systemd[1]: Starting RealtimeKit Scheduling Policy Service...
mai 14 14:16:23 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
mai 14 14:16:23 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:23 Arch-PC systemd[1]: Started RealtimeKit Scheduling Policy Service.
mai 14 14:16:23 Arch-PC kernel: audit: type=1130 audit(1589476583.865:60): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Successfully called chroot.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Successfully dropped privileges.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Successfully limited resources.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Running.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Canary thread running.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Watchdog thread running.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Successfully made thread 779 of process 779 owned by '120' high priority at nice level -11.
mai 14 14:16:23 Arch-PC rtkit-daemon[800]: Supervising 1 threads of 1 processes of 1 users.
mai 14 14:16:24 Arch-PC rtkit-daemon[800]: Supervising 1 threads of 1 processes of 1 users.
mai 14 14:16:24 Arch-PC rtkit-daemon[800]: Successfully made thread 803 of process 779 owned by '120' RT at priority 5.
mai 14 14:16:24 Arch-PC rtkit-daemon[800]: Supervising 2 threads of 1 processes of 1 users.
mai 14 14:16:24 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.23' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:24 Arch-PC systemd[1]: Starting Location Lookup Service...
mai 14 14:16:24 Arch-PC polkitd[535]: Registered Authentication Agent for unix-session:c1 (system bus name :1.23 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 14 14:16:24 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.23' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:16:24 Arch-PC systemd[1]: Starting PackageKit Daemon...
mai 14 14:16:24 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.31' (uid=967 pid=804 comm="/usr/lib/geoclue ")
mai 14 14:16:24 Arch-PC systemd[1]: Starting WPA supplicant...
mai 14 14:16:24 Arch-PC PackageKit[805]: daemon start
mai 14 14:16:24 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.PackageKit'
mai 14 14:16:24 Arch-PC systemd[1]: Started PackageKit Daemon.
mai 14 14:16:24 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:24 Arch-PC kernel: audit: type=1130 audit(1589476584.919:61): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:25 Arch-PC rtkit-daemon[800]: Supervising 2 threads of 1 processes of 1 users.
mai 14 14:16:25 Arch-PC rtkit-daemon[800]: Successfully made thread 813 of process 779 owned by '120' RT at priority 5.
mai 14 14:16:25 Arch-PC rtkit-daemon[800]: Supervising 3 threads of 1 processes of 1 users.
mai 14 14:16:25 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' (uid=120 pid=779 comm="/usr/bin/pulseaudio --daemonize=no ")
mai 14 14:16:25 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
mai 14 14:16:25 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
mai 14 14:16:25 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:25 Arch-PC systemd[1]: Started WPA supplicant.
mai 14 14:16:25 Arch-PC wpa_supplicant[809]: Successfully initialized wpa_supplicant
mai 14 14:16:25 Arch-PC kernel: audit: type=1130 audit(1589476585.349:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:25 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
mai 14 14:16:25 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:25 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.31' (uid=967 pid=804 comm="/usr/lib/geoclue ")
mai 14 14:16:25 Arch-PC systemd[1]: Started Location Lookup Service.
mai 14 14:16:25 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 14 14:16:25 Arch-PC kernel: audit: type=1130 audit(1589476585.355:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:25 Arch-PC geoclue[804]: Failed to connect to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 14 14:16:25 Arch-PC systemd[565]: Started Sound Service.
mai 14 14:16:25 Arch-PC pulseaudio[779]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.gnome.Shell.Notifications' requested by ':1.2' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[680]: dbus-daemon[680]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[680]: dbus-daemon[680]: Successfully activated service 'org.a11y.atspi.Registry'
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[822]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
mai 14 14:16:26 Arch-PC gnome-shell[650]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Successfully activated service 'org.gnome.Shell.Notifications'
mai 14 14:16:26 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.38' (uid=120 pid=835 comm="/usr/lib/gsd-rfkill ")
mai 14 14:16:26 Arch-PC audit: AUDIT1334 prog-id=17 op=LOAD
mai 14 14:16:26 Arch-PC audit: AUDIT1334 prog-id=18 op=LOAD
mai 14 14:16:26 Arch-PC systemd[1]: Starting Hostname Service...
mai 14 14:16:26 Arch-PC kernel: audit: type=1334 audit(1589476586.922:64): prog-id=17 op=LOAD
mai 14 14:16:26 Arch-PC kernel: audit: type=1334 audit(1589476586.922:65): prog-id=18 op=LOAD
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.10' (uid=120 pid=823 comm="/usr/lib/gsd-sharing ")
mai 14 14:16:26 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:16:26 Arch-PC gsd-sharing[823]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:16:26 Arch-PC gsd-sharing[823]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:16:26 Arch-PC gsd-sharing[823]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:16:27 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.hostname1'
mai 14 14:16:27 Arch-PC systemd[1]: Started Hostname Service.
mai 14 14:16:27 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:27 Arch-PC kernel: audit: type=1130 audit(1589476587.405:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:27 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:16:29 Arch-PC gnome-shell[650]: Registering session with GDM
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[943]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[943]: > Internal error: Could not resolve keysym XF86FullScreen
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[943]: Errors from xkbcomp are not fatal to the X server
mai 14 14:16:30 Arch-PC gnome-shell[650]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:16:30 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=650 comm="/usr/bin/gnome-shell ")
mai 14 14:16:30 Arch-PC /usr/lib/gdm-wayland-session[613]: dbus-daemon[613]: [session uid=120 pid=613] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:16:30 Arch-PC gnome-shell[650]: Could not issue 'StartUnit' systemd call
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[947]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[947]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[947]: > X11 cannot support keycodes above 255.
mai 14 14:16:30 Arch-PC org.gnome.Shell.desktop[947]: Errors from xkbcomp are not fatal to the X server
mai 14 14:16:31 Arch-PC emby-server[510]: Info Skia: SkiaSharp version: 1.68.0.0
mai 14 14:16:31 Arch-PC emby-server[510]: Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 05/15/2020 02:00:00, which is 703.4780966516666 minutes from now.
mai 14 14:16:31 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.47' (uid=120 pid=828 comm="/usr/lib/gsd-color ")
mai 14 14:16:31 Arch-PC gnome-session-binary[614]: Entering running state
mai 14 14:16:31 Arch-PC systemd[1]: Starting Manage, Install and Generate Color Profiles...
mai 14 14:16:31 Arch-PC xbrlapi.desktop[962]: openConnection: connect: Arquivo ou diretório inexistente
mai 14 14:16:31 Arch-PC xbrlapi.desktop[962]: cannot connect to braille devices daemon brltty at :0
mai 14 14:16:31 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.ColorManager'
mai 14 14:16:31 Arch-PC systemd[1]: Started Manage, Install and Generate Color Profiles.
mai 14 14:16:31 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:31 Arch-PC kernel: audit: type=1130 audit(1589476591.779:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:32 Arch-PC gsd-media-keys[840]: Failed to grab accelerator for keybinding settings:playback-random
mai 14 14:16:32 Arch-PC gsd-media-keys[840]: Failed to grab accelerator for keybinding settings:rfkill
mai 14 14:16:32 Arch-PC gsd-media-keys[840]: Failed to grab accelerator for keybinding settings:hibernate
mai 14 14:16:32 Arch-PC gsd-media-keys[840]: Failed to grab accelerator for keybinding settings:playback-repeat
mai 14 14:16:32 Arch-PC emby-server[510]: Info TaskManager: Daily trigger for Rotate log file set to fire at 05/15/2020 00:00:00, which is 583.464144325 minutes from now.
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: ServerId: 8e7e254f5c794322ae147b1029f81496
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Init BeginReceive on 0.0.0.0
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.2120412 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Loading data from /var/lib/emby/data/connect.txt
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Loading data from /var/lib/emby/data/wan.dat
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0091984 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Core startup complete
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Post-init migrations complete
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0007124 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Security.PluginSecurityManager
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 5.19E-05 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0001491 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point NfoMetadata.EntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0005547 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Webhooks.WebhooksEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Webhooks.WebhooksEntryPoint. Duration: 0.0026187 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 5.61E-05 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0015102 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistsEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistsEntryPoint. Duration: 0.0012263 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0001872 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0005902 seconds
mai 14 14:16:32 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup
mai 14 14:16:33 Arch-PC gnome-shell[650]: ../mutter/clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
mai 14 14:16:33 Arch-PC emby-server[510]: Info HttpClient: GET https://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.7106295 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0003669 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0002056 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0026639 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0038431 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0006015 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0008095 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0001839 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0030696 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.LiveTV.EntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info LiveTV: Loading live tv data from /var/lib/emby/data/livetv/timers
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.03242 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.LiveTV.LiveTVEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.LiveTV.LiveTVEntryPoint. Duration: 0.0002756 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.LiveTV.RecordingNotifier
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0025677 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0040206 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.3376621 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Notifications.Notifications
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0004709 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: SyncRepository Initialize taking write lock
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: SyncRepository Initialize write lock taken
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0066645 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0032322 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0003959 seconds
mai 14 14:16:33 Arch-PC emby-server[510]: Info App: All entry points have started
mai 14 14:16:36 Arch-PC gnome-shell[650]: Warning: Failed to start gsd-xsettings
mai 14 14:16:36 Arch-PC gnome-shell[650]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
mai 14 14:16:36 Arch-PC gdm-password][948]: gkr-pam: unable to locate daemon control file
mai 14 14:16:36 Arch-PC audit[948]: USER_AUTH pid=948 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:36 Arch-PC gdm-password][948]: gkr-pam: stashed password to try later in open session
mai 14 14:16:36 Arch-PC kernel: audit: type=1100 audit(1589476596.785:68): pid=948 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:36 Arch-PC audit[948]: USER_ACCT pid=948 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:36 Arch-PC kernel: audit: type=1101 audit(1589476596.919:69): pid=948 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:36 Arch-PC audit[948]: CRED_ACQ pid=948 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:36 Arch-PC kernel: audit: type=1103 audit(1589476596.922:70): pid=948 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:37 Arch-PC kernel: audit: type=1006 audit(1589476597.075:71): pid=948 uid=0 old-auid=4294967295 auid=1003 tty=(none) old-ses=4294967295 ses=2 res=1
mai 14 14:16:37 Arch-PC gdm-password][948]: pam_unix(gdm-password:session): session opened for user stalker by (uid=0)
mai 14 14:16:37 Arch-PC systemd[1]: Created slice User Slice of UID 1003.
mai 14 14:16:37 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/1003...
mai 14 14:16:37 Arch-PC systemd-logind[499]: New session 2 of user stalker.
mai 14 14:16:37 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/1003.
mai 14 14:16:37 Arch-PC systemd[1]: Starting User Manager for UID 1003...
mai 14 14:16:37 Arch-PC kernel: audit: type=1130 audit(1589476597.105:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC audit[990]: USER_ACCT pid=990 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC systemd[990]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[stalker] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:16:37 Arch-PC audit[990]: CRED_ACQ pid=990 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:16:37 Arch-PC kernel: audit: type=1101 audit(1589476597.115:73): pid=990 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC kernel: audit: type=1103 audit(1589476597.115:74): pid=990 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:16:37 Arch-PC kernel: audit: type=1006 audit(1589476597.115:75): pid=990 uid=0 old-auid=4294967295 auid=1003 tty=(none) old-ses=4294967295 ses=3 res=1
mai 14 14:16:37 Arch-PC systemd[990]: pam_unix(systemd-user:session): session opened for user stalker by (uid=0)
mai 14 14:16:37 Arch-PC audit[990]: USER_START pid=990 uid=0 auid=1003 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC kernel: audit: type=1105 audit(1589476597.119:76): pid=990 uid=0 auid=1003 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC audit: AUDIT1334 prog-id=19 op=LOAD
mai 14 14:16:37 Arch-PC kernel: audit: type=1334 audit(1589476597.125:77): prog-id=19 op=LOAD
mai 14 14:16:37 Arch-PC audit: AUDIT1334 prog-id=19 op=UNLOAD
mai 14 14:16:37 Arch-PC systemd[990]: Reached target Paths.
mai 14 14:16:39 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:16:37 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC audit[948]: USER_START pid=948 uid=0 auid=1003 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:16:37 Arch-PC audit[948]: USER_LOGIN pid=948 uid=0 auid=1003 ses=2 msg='uid=1003 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:16:37 Arch-PC systemd[990]: Reached target Timers.
mai 14 14:16:37 Arch-PC gdm-password][948]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
mai 14 14:16:37 Arch-PC systemd[990]: Starting D-Bus User Message Bus Socket.
mai 14 14:16:37 Arch-PC systemd[990]: Listening on GnuPG network certificate management daemon.
mai 14 14:16:37 Arch-PC systemd[990]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:16:37 Arch-PC systemd[990]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:16:37 Arch-PC systemd[990]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:16:37 Arch-PC systemd[990]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 14:16:37 Arch-PC systemd[990]: Listening on p11-kit server.
mai 14 14:16:37 Arch-PC systemd[990]: Listening on Multimedia System.
mai 14 14:16:37 Arch-PC systemd[990]: Listening on Sound System.
mai 14 14:16:37 Arch-PC systemd[990]: Listening on D-Bus User Message Bus Socket.
mai 14 14:16:37 Arch-PC systemd[990]: Reached target Sockets.
mai 14 14:16:37 Arch-PC systemd[990]: Reached target Basic System.
mai 14 14:16:37 Arch-PC systemd[1]: Started User Manager for UID 1003.
mai 14 14:16:37 Arch-PC systemd[1]: Started Session 2 of user stalker.
mai 14 14:16:37 Arch-PC systemd[990]: Starting Update XDG user dir configuration...
mai 14 14:16:37 Arch-PC systemd[990]: xdg-user-dirs-update.service: Succeeded.
mai 14 14:16:37 Arch-PC systemd[990]: Finished Update XDG user dir configuration.
mai 14 14:16:37 Arch-PC systemd[990]: Reached target Main User Target.
mai 14 14:16:37 Arch-PC systemd[990]: Startup finished in 412ms.
mai 14 14:16:38 Arch-PC systemd[990]: Started D-Bus User Message Bus.
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session-pre.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session-initialized.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session@gnome-initial-setup.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:16:40 Arch-PC gnome-session-binary[1058]: WARNING: Could not parse desktop file kaccess.desktop or it references a not found TryExec binary
mai 14 14:16:40 Arch-PC gnome-session[1058]: gnome-session-binary[1058]: WARNING: Could not parse desktop file kaccess.desktop or it references a not found TryExec binary
mai 14 14:16:40 Arch-PC gnome-session[1058]: gnome-session-binary[1058]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session@gnome-login.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Successfully made thread 1057 of process 1057 owned by '1003' high priority at nice level -11.
mai 14 14:16:40 Arch-PC pulseaudio[1057]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session-failed.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session-wayland.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:16:40 Arch-PC gnome-session-binary[1058]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
mai 14 14:16:39 Arch-PC systemd[990]: gnome-session@gnome.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:16:39 Arch-PC systemd[990]: Created slice gnome\x2dsession\x2dmanager.slice.
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Successfully made thread 1080 of process 1057 owned by '1003' RT at priority 5.
mai 14 14:16:39 Arch-PC systemd[990]: Reached target Session services which should run early before the graphical session is brought up.
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:16:39 Arch-PC systemd[990]: Starting Monitor Session leader for GNOME Session...
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:16:41 Arch-PC gnome-keyring-ssh.desktop[1071]: SSH_AUTH_SOCK=/run/user/1003/keyring/ssh
mai 14 14:16:39 Arch-PC systemd[990]: Starting Sound Service...
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Successfully made thread 1081 of process 1057 owned by '1003' RT at priority 5.
mai 14 14:16:39 Arch-PC gnome-session-c[1056]: Error creating FIFO: Arquivo existe
mai 14 14:16:40 Arch-PC rtkit-daemon[800]: Supervising 6 threads of 2 processes of 2 users.
mai 14 14:16:39 Arch-PC systemd[990]: Started Monitor Session leader for GNOME Session.
mai 14 14:16:40 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.62' (uid=1003 pid=1057 comm="/usr/bin/pulseaudio --daemonize=no ")
mai 14 14:16:39 Arch-PC systemd[990]: Reached target Tasks to be run before GNOME Session starts.
mai 14 14:16:40 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
mai 14 14:16:39 Arch-PC systemd[990]: Starting GNOME Session Manager (session: gnome)...
mai 14 14:16:41 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.12' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:40 Arch-PC systemd[990]: Started GNOME Session Manager (session: gnome).
mai 14 14:16:41 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.a11y.Bus'
mai 14 14:16:40 Arch-PC systemd[990]: Reached target GNOME Session Manager is ready.
mai 14 14:16:40 Arch-PC systemd[990]: Starting GNOME Shell on Wayland...
mai 14 14:16:40 Arch-PC systemd[990]: Started Sound Service.
mai 14 14:16:41 Arch-PC systemd[990]: Starting Accessibility services bus...
mai 14 14:16:41 Arch-PC systemd[990]: Started Accessibility services bus.
mai 14 14:16:41 Arch-PC gnome-shell[1105]: glamor: No eglstream capable devices found
mai 14 14:16:44 Arch-PC gnome-shell[1073]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mai 14 14:16:44 Arch-PC gnome-shell[1073]: Will monitor session 2
mai 14 14:16:45 Arch-PC gnome-shell[1073]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating service name='ca.desrt.dconf' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'ca.desrt.dconf'
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:45 Arch-PC systemd[990]: Starting sandboxed app permission store...
mai 14 14:16:45 Arch-PC systemd[990]: Started sandboxed app permission store.
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.16' (uid=1003 pid=1120 comm="/usr/lib/gnome-shell-calendar-server ")
mai 14 14:16:45 Arch-PC polkitd[535]: Registered Authentication Agent for unix-session:2 (system bus name :1.59 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 14 14:16:45 Arch-PC systemd[990]: Starting Evolution source registry...
mai 14 14:16:45 Arch-PC gnome-shell[1073]: Telepathy is not available, chat integration will be disabled.
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:45 Arch-PC systemd[990]: Starting Virtual filesystem service...
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gtk.vfs.Daemon'
mai 14 14:16:45 Arch-PC systemd[990]: Started Virtual filesystem service.
mai 14 14:16:45 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:45 Arch-PC systemd[990]: Starting Virtual filesystem service - disk device monitor...
mai 14 14:16:45 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.63' (uid=1003 pid=1134 comm="/usr/lib/gvfs-udisks2-volume-monitor ")
mai 14 14:16:45 Arch-PC systemd[1]: Starting Disk Manager...
mai 14 14:16:46 Arch-PC udisksd[1144]: udisks daemon version 2.8.4 starting
mai 14 14:16:46 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating service name='org.gnome.OnlineAccounts' requested by ':1.17' (uid=1003 pid=1124 comm="/usr/lib/evolution-source-registry ")
mai 14 14:16:47 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
mai 14 14:16:47 Arch-PC systemd[990]: Started Evolution source registry.
mai 14 14:16:47 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.Shell.CalendarServer'
mai 14 14:16:47 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.UDisks2'
mai 14 14:16:47 Arch-PC systemd[1]: Started Disk Manager.
mai 14 14:16:47 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:47 Arch-PC udisksd[1144]: Acquired the name org.freedesktop.UDisks2 on the system message bus
mai 14 14:16:47 Arch-PC kernel: kauditd_printk_skb: 4 callbacks suppressed
mai 14 14:16:47 Arch-PC kernel: audit: type=1130 audit(1589476607.315:82): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:47 Arch-PC goa-daemon[1150]: goa-daemon version 3.36.0 starting
mai 14 14:16:47 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating service name='org.gnome.Identity' requested by ':1.21' (uid=1003 pid=1150 comm="/usr/lib/goa-daemon ")
mai 14 14:16:47 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.OnlineAccounts'
mai 14 14:16:47 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.Identity'
mai 14 14:16:48 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
mai 14 14:16:48 Arch-PC systemd[990]: Started Virtual filesystem service - disk device monitor.
mai 14 14:16:48 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating service name='org.gnome.Shell.Notifications' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:48 Arch-PC at-spi-bus-launcher[1102]: dbus-daemon[1102]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:16:48 Arch-PC at-spi-bus-launcher[1102]: dbus-daemon[1102]: Successfully activated service 'org.a11y.atspi.Registry'
mai 14 14:16:48 Arch-PC at-spi-bus-launcher[1192]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
mai 14 14:16:48 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.16' (uid=1003 pid=1120 comm="/usr/lib/gnome-shell-calendar-server ")
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Shell on Wayland.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Shell on Wayland.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Session is initialized.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Wayland Session.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Session (session: gnome).
mai 14 14:16:48 Arch-PC systemd[990]: Starting Evolution calendar service...
mai 14 14:16:48 Arch-PC systemd[990]: Starting Signal initialization done to GNOME Session Manager...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Accessibility settings...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Color management...
mai 14 14:16:48 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.Shell.Notifications'
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Date & Time handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Maintenance of expirable data...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Keyboard handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Media keys handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Power management handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Printer notifications...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME RFKill handling...
mai 14 14:16:48 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Freedesktop screensaver handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Sharing handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Smartcard handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Sound sample caching handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME USB protection handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME Wacom handling...
mai 14 14:16:48 Arch-PC systemd[990]: Starting GNOME WWan management...
mai 14 14:16:48 Arch-PC gnome-session-binary[1058]: Entering running state
mai 14 14:16:48 Arch-PC systemd[990]: gnome-session-signal-init.service: Succeeded.
mai 14 14:16:48 Arch-PC systemd[990]: Finished Signal initialization done to GNOME Session Manager.
mai 14 14:16:48 Arch-PC gnome-shell[1073]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Accessibility settings.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME RFKill handling.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Accessibility settings.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME RFKill handling.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Printer notifications.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Printer notifications.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Smartcard handling.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Smartcard handling.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Freedesktop screensaver handling.
mai 14 14:16:48 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.44' (uid=1003 pid=1269 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free")
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Freedesktop screensaver handling.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Date & Time handling.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Date & Time handling.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Sharing handling.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Sharing handling.
mai 14 14:16:48 Arch-PC NetworkManager[495]: <info> [1589476608.7058] agent-manager: agent[d9d729fddad88199,:1.59/org.gnome.Shell.NetworkAgent/1003]: agent registered
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Maintenance of expirable data.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Maintenance of expirable data.
mai 14 14:16:48 Arch-PC systemd[990]: Started GNOME Sound sample caching handling.
mai 14 14:16:48 Arch-PC systemd[990]: Reached target GNOME Sound sample caching handling.
mai 14 14:16:49 Arch-PC systemd[990]: Started GNOME USB protection handling.
mai 14 14:16:49 Arch-PC systemd[990]: Reached target GNOME USB protection handling.
mai 14 14:16:49 Arch-PC systemd[990]: Starting Tracker metadata database store and lookup manager...
mai 14 14:16:49 Arch-PC systemd[990]: Started GNOME WWan management.
mai 14 14:16:49 Arch-PC systemd[990]: Reached target GNOME WWan management.
mai 14 14:16:50 Arch-PC systemd[990]: Started GNOME Keyboard handling.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Keyboard handling.
mai 14 14:16:50 Arch-PC systemd[990]: Started GNOME Color management.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Color management.
mai 14 14:16:50 Arch-PC systemd[990]: Started GNOME Media keys handling.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Media keys handling.
mai 14 14:16:50 Arch-PC systemd[990]: Started GNOME Power management handling.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Power management handling.
mai 14 14:16:50 Arch-PC systemd[990]: Started GNOME Wacom handling.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Wacom handling.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Session.
mai 14 14:16:50 Arch-PC systemd[990]: Reached target GNOME Wayland Session (session: gnome).
mai 14 14:16:50 Arch-PC systemd[990]: Reached target Current graphical user session.
mai 14 14:16:50 Arch-PC gnome-shell[650]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:16:50 Arch-PC gsd-media-keys[1217]: Failed to grab accelerator for keybinding settings:playback-random
mai 14 14:16:50 Arch-PC gsd-media-keys[1217]: Failed to grab accelerator for keybinding settings:rfkill
mai 14 14:16:50 Arch-PC gsd-media-keys[1217]: Failed to grab accelerator for keybinding settings:hibernate
mai 14 14:16:50 Arch-PC gsd-media-keys[1217]: Failed to grab accelerator for keybinding settings:playback-repeat
mai 14 14:16:50 Arch-PC gnome-shell[650]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:16:50 Arch-PC kernel: UDF-fs: INFO Mounting volume 'Sepultura - Chaos DVD', timestamp 2013/04/18 17:39 (1000)
mai 14 14:16:51 Arch-PC systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice.
mai 14 14:16:51 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clean-mount-point@media-Sepultura\x20\x2d\x20Chaos\x20DVD comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:51 Arch-PC systemd[1]: Finished Clean the /media/Sepultura - Chaos DVD mount point.
mai 14 14:16:51 Arch-PC kernel: audit: type=1130 audit(1589476611.169:83): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clean-mount-point@media-Sepultura\x20\x2d\x20Chaos\x20DVD comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:51 Arch-PC gnome-shell[1073]: GNOME Shell started at Thu May 14 2020 14:16:48 GMT-0300 (Horário Padrão de Brasília)
mai 14 14:16:51 Arch-PC gnome-shell[1073]: Registering session with GDM
mai 14 14:16:51 Arch-PC udisksd[1144]: Mounted /dev/sr0 at /media/Sepultura - Chaos DVD on behalf of uid 1003
mai 14 14:16:51 Arch-PC audit[545]: USER_END pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:51 Arch-PC audit[545]: CRED_DISP pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:51 Arch-PC kernel: audit: type=1106 audit(1589476611.222:84): pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:51 Arch-PC kernel: audit: type=1104 audit(1589476611.222:85): pid=545 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:16:51 Arch-PC systemd-logind[499]: Session c1 logged out. Waiting for processes to exit.
mai 14 14:16:51 Arch-PC polkitd[535]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.23, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus)
mai 14 14:16:51 Arch-PC systemd[565]: pulseaudio.service: Succeeded.
mai 14 14:16:51 Arch-PC systemd[1]: session-c1.scope: Succeeded.
mai 14 14:16:51 Arch-PC systemd-logind[499]: Removed session c1.
mai 14 14:16:51 Arch-PC tracker-extract[1239]: Set scheduler policy to SCHED_IDLE
mai 14 14:16:51 Arch-PC tracker-extract[1239]: Setting priority nice level to 19
mai 14 14:16:51 Arch-PC tracker-miner-f[1229]: Set scheduler policy to SCHED_IDLE
mai 14 14:16:51 Arch-PC tracker-miner-f[1229]: Setting priority nice level to 19
mai 14 14:16:52 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.freedesktop.Tracker1'
mai 14 14:16:52 Arch-PC tracker-store.desktop[1269]: (uint32 1,)
mai 14 14:16:52 Arch-PC systemd[990]: Started Tracker metadata database store and lookup manager.
mai 14 14:16:52 Arch-PC gnome-shell[1372]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:16:52 Arch-PC gnome-shell[1372]: > Internal error: Could not resolve keysym XF86FullScreen
mai 14 14:16:52 Arch-PC gnome-shell[1372]: Errors from xkbcomp are not fatal to the X server
mai 14 14:16:52 Arch-PC gnome-shell[1073]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:16:52 Arch-PC gnome-shell[1374]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:16:52 Arch-PC gnome-shell[1374]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:16:52 Arch-PC gnome-shell[1374]: > X11 cannot support keycodes above 255.
mai 14 14:16:52 Arch-PC gnome-shell[1374]: > Internal error: Could not resolve keysym Invalid
mai 14 14:16:52 Arch-PC gnome-shell[1374]: Errors from xkbcomp are not fatal to the X server
mai 14 14:16:52 Arch-PC systemd[990]: GNOME session X11 services is not active.
mai 14 14:16:52 Arch-PC systemd[990]: Dependency failed for GNOME XSettings.
mai 14 14:16:52 Arch-PC systemd[990]: gsd-xsettings.target: Job gsd-xsettings.target/start failed with result 'dependency'.
mai 14 14:16:52 Arch-PC systemd[990]: Starting GNOME XSettings...
mai 14 14:16:52 Arch-PC systemd[990]: Started GNOME XSettings.
mai 14 14:16:53 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
mai 14 14:16:53 Arch-PC systemd[990]: Started Evolution calendar service.
mai 14 14:16:53 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.38' (uid=1003 pid=1201 comm="/usr/lib/evolution-calendar-factory ")
mai 14 14:16:53 Arch-PC systemd[990]: Starting Evolution address book service...
mai 14 14:16:53 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
mai 14 14:16:53 Arch-PC systemd[990]: Started Evolution address book service.
mai 14 14:16:55 Arch-PC octopi-notifier[1254]: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
mai 14 14:16:55 Arch-PC gnome-software[1215]: plugin appstream took 1,3 seconds to do setup
mai 14 14:16:55 Arch-PC gnome-software[1215]: enabled plugins: desktop-categories, fwupd, os-release, provenance, appstream, provenance-license, desktop-menu-path, flatpak, generic-updates, hardcoded-blacklist, hardcoded-popular, modalias, rewrite-resource, icons, malcontent, odrs, key-colors, key-colors-metadata
mai 14 14:16:55 Arch-PC gnome-software[1215]: disabled plugins: dpkg, dummy, fedora-langpacks, fedora-pkgdb-collections, repos
mai 14 14:16:55 Arch-PC octopi-notifier[1254]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
mai 14 14:16:55 Arch-PC kernel: audit: type=1701 audit(1589476615.752:86): auid=1003 uid=1003 gid=1003 ses=3 pid=1254 comm="octopi-notifier" exe="/usr/bin/octopi-notifier" sig=6 res=1
mai 14 14:16:55 Arch-PC audit[1254]: ANOM_ABEND auid=1003 uid=1003 gid=1003 ses=3 pid=1254 comm="octopi-notifier" exe="/usr/bin/octopi-notifier" sig=6 res=1
mai 14 14:16:55 Arch-PC octopi-notifier[1254]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
mai 14 14:16:55 Arch-PC systemd[1]: Created slice system-systemd\x2dcoredump.slice.
mai 14 14:16:56 Arch-PC kernel: audit: type=1334 audit(1589476615.852:87): prog-id=20 op=LOAD
mai 14 14:16:56 Arch-PC kernel: audit: type=1334 audit(1589476615.852:88): prog-id=21 op=LOAD
mai 14 14:16:56 Arch-PC kernel: audit: type=1130 audit(1589476615.852:89): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1426-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:55 Arch-PC audit: AUDIT1334 prog-id=20 op=LOAD
mai 14 14:16:55 Arch-PC audit: AUDIT1334 prog-id=21 op=LOAD
mai 14 14:16:55 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1426-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:55 Arch-PC systemd[1]: Started Process Core Dump (PID 1426/UID 0).
mai 14 14:16:56 Arch-PC systemd-coredump[1429]: Process 1254 (octopi-notifier) of user 1003 dumped core.
Stack trace of thread 1254:
#0 0x00007f55fa3432e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007f55fa32c853 abort (libc.so.6 + 0x25853)
#2 0x00007f55faaba9ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007f55fb2fa0e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007f55fb2fa581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007f55face32e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007f55fb2fd5c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007f55fb9fb67a _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x16167a)
#8 0x000055b57087189e main (octopi-notifier + 0x1489e)
#9 0x00007f55fa32e002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x000055b5708713be _start (octopi-notifier + 0x143be)
mai 14 14:16:57 Arch-PC kernel: audit: type=1131 audit(1589476616.965:90): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1426-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:56 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1426-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:56 Arch-PC systemd[1]: systemd-coredump@0-1426-0.service: Succeeded.
mai 14 14:16:57 Arch-PC audit: AUDIT1334 prog-id=21 op=UNLOAD
mai 14 14:16:57 Arch-PC audit: AUDIT1334 prog-id=20 op=UNLOAD
mai 14 14:16:57 Arch-PC kernel: audit: type=1334 audit(1589476617.465:91): prog-id=21 op=UNLOAD
mai 14 14:16:57 Arch-PC kernel: audit: type=1334 audit(1589476617.465:92): prog-id=20 op=UNLOAD
mai 14 14:16:57 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.85' (uid=1003 pid=1215 comm="/usr/bin/gnome-software --gapplication-service ")
mai 14 14:16:57 Arch-PC systemd[1]: Starting Firmware update daemon...
mai 14 14:16:58 Arch-PC fwupd[1448]: 17:16:58:0475 FuPluginUefi kernel efivars support missing: /sys/firmware/efi/efivars
mai 14 14:16:58 Arch-PC fwupd[1448]: 17:16:58:0549 FuEngine failed to add udev device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/0003:046D:C077.0003/hidraw/hidraw2: failed to ping Logitech USB Optical Mouse: failed to send: failed to write: wrote -1 of 7
mai 14 14:16:58 Arch-PC fwupd[1448]: 17:16:58:0552 FuEngine failed to add udev device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/0003:046D:C31C.0001/hidraw/hidraw0: failed to ping Logitech USB Keyboard: failed to send: failed to write: wrote -1 of 7
mai 14 14:16:58 Arch-PC fwupd[1448]: 17:16:58:0554 FuEngine failed to add udev device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/hidraw/hidraw1: failed to ping Logitech USB Keyboard: failed to send: failed to write: wrote -1 of 7
mai 14 14:16:58 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.fwupd'
mai 14 14:16:58 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fwupd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:16:58 Arch-PC systemd[1]: Started Firmware update daemon.
mai 14 14:16:58 Arch-PC kernel: audit: type=1130 audit(1589476618.759:93): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fwupd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Builder.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Calculator.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.clocks.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Dictionary.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Documents.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Evince/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.gedit.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Maps.desktop/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: adding wildcard app */*/*/*/org.gnome.Weather/* to plugin cache
mai 14 14:17:00 Arch-PC gnome-software[1215]: hiding category graphics featured applications: found only 0 to show, need at least 9
mai 14 14:17:00 Arch-PC gnome-software[1215]: hiding category games featured applications: found only 0 to show, need at least 9
mai 14 14:17:01 Arch-PC systemd[1]: Stopping User Manager for UID 120...
mai 14 14:17:01 Arch-PC systemd[565]: Stopped target Main User Target.
mai 14 14:17:01 Arch-PC systemd[565]: Stopping D-Bus User Message Bus...
mai 14 14:17:01 Arch-PC systemd[565]: dbus.service: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Stopped D-Bus User Message Bus.
mai 14 14:17:01 Arch-PC systemd[565]: Stopped target Basic System.
mai 14 14:17:01 Arch-PC systemd[565]: Stopped target Paths.
mai 14 14:17:01 Arch-PC systemd[565]: Stopped target Sockets.
mai 14 14:17:01 Arch-PC systemd[565]: Stopped target Timers.
mai 14 14:17:01 Arch-PC systemd[565]: dbus.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed D-Bus User Message Bus Socket.
mai 14 14:17:01 Arch-PC systemd[565]: dirmngr.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed GnuPG network certificate management daemon.
mai 14 14:17:01 Arch-PC systemd[565]: gpg-agent-browser.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:17:01 Arch-PC systemd[565]: gpg-agent-extra.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:17:01 Arch-PC systemd[565]: gpg-agent-ssh.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:17:01 Arch-PC systemd[565]: gpg-agent.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed GnuPG cryptographic agent and passphrase cache.
mai 14 14:17:01 Arch-PC systemd[565]: p11-kit-server.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed p11-kit server.
mai 14 14:17:01 Arch-PC systemd[565]: pipewire.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed Multimedia System.
mai 14 14:17:01 Arch-PC systemd[565]: pulseaudio.socket: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Closed Sound System.
mai 14 14:17:01 Arch-PC systemd[565]: Reached target Shutdown.
mai 14 14:17:01 Arch-PC systemd[565]: systemd-exit.service: Succeeded.
mai 14 14:17:01 Arch-PC systemd[565]: Finished Exit the Session.
mai 14 14:17:01 Arch-PC systemd[565]: Reached target Exit the Session.
mai 14 14:17:01 Arch-PC systemd[572]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:17:01 Arch-PC systemd[1]: user@120.service: Succeeded.
mai 14 14:17:01 Arch-PC systemd[1]: Stopped User Manager for UID 120.
mai 14 14:17:01 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:01 Arch-PC systemd[1]: Stopping User Runtime Directory /run/user/120...
mai 14 14:17:01 Arch-PC kernel: audit: type=1131 audit(1589476621.462:94): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:01 Arch-PC systemd[990]: run-user-120.mount: Succeeded.
mai 14 14:17:01 Arch-PC kernel: audit: type=1131 audit(1589476621.489:95): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:01 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:01 Arch-PC systemd[1]: run-user-120.mount: Succeeded.
mai 14 14:17:01 Arch-PC systemd[1]: user-runtime-dir@120.service: Succeeded.
mai 14 14:17:01 Arch-PC systemd[1]: Stopped User Runtime Directory /run/user/120.
mai 14 14:17:01 Arch-PC systemd[1]: Removed slice User Slice of UID 120.
mai 14 14:17:01 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating service name='org.gnome.Nautilus' requested by ':1.11' (uid=1003 pid=1073 comm="/usr/bin/gnome-shell ")
mai 14 14:17:03 Arch-PC baloo_file.desktop[1213]: Baloo File Indexing has been disabled
mai 14 14:17:04 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.Nautilus'
mai 14 14:17:05 Arch-PC nautilus[1466]: Unable to get contents of the bookmarks file: Erro ao abrir arquivo /home/stalker/.gtk-bookmarks: No such file or directory
mai 14 14:17:16 Arch-PC gnome-software[1215]: Only 2 apps for popular list, hiding
mai 14 14:17:16 Arch-PC gnome-software[1215]: not GsPlugin error g-io-error-quark:15: failed to process components/component/id[text()='archlinux.www.Arch Linux-(null)']/../pkgname/..|components/component[@type='webapp']/id[text()='archlinux.www.Arch Linux-(null)']/..|component/id[text()='archlinux.www.Arch Linux-(null)']/..: cannot parse text or number `null`
mai 14 14:17:16 Arch-PC gnome-software[1215]: not GsPlugin error g-io-error-quark:15: failed to process components/component/id[text()='archlinux.www.Arch Linux-(null)']/../pkgname/..|components/component[@type='webapp']/id[text()='archlinux.www.Arch Linux-(null)']/..|component/id[text()='archlinux.www.Arch Linux-(null)']/..: cannot parse text or number `null`
mai 14 14:17:16 Arch-PC gnome-software[1215]: not GsPlugin error g-io-error-quark:15: failed to process components/component/id[text()='archlinux.www.Arch Linux-(null)']/../pkgname/..|components/component[@type='webapp']/id[text()='archlinux.www.Arch Linux-(null)']/..|component/id[text()='archlinux.www.Arch Linux-(null)']/..: cannot parse text or number `null`
mai 14 14:17:16 Arch-PC gnome-software[1215]: not handling error failed for action refine: failed to process components/component/id[text()='archlinux.www.Arch Linux-(null)']/../pkgname/..|components/component[@type='webapp']/id[text()='archlinux.www.Arch Linux-(null)']/..|component/id[text()='archlinux.www.Arch Linux-(null)']/..: cannot parse text or number `null`
mai 14 14:17:22 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.57' (uid=1003 pid=1229 comm="/usr/lib/tracker-miner-fs ")
mai 14 14:17:22 Arch-PC systemd[990]: Starting Tracker metadata extractor...
mai 14 14:17:22 Arch-PC tracker-extract[1549]: Set scheduler policy to SCHED_IDLE
mai 14 14:17:22 Arch-PC tracker-extract[1549]: Setting priority nice level to 19
mai 14 14:17:23 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
mai 14 14:17:23 Arch-PC systemd[990]: Started Tracker metadata extractor.
mai 14 14:17:23 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.67' (uid=1003 pid=1549 comm="/usr/lib/tracker-extract ")
mai 14 14:17:23 Arch-PC systemd[990]: Starting Virtual filesystem metadata service...
mai 14 14:17:23 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gtk.vfs.Metadata'
mai 14 14:17:23 Arch-PC systemd[990]: Started Virtual filesystem metadata service.
mai 14 14:17:25 Arch-PC geoclue[804]: Service not used for 60 seconds. Shutting down..
mai 14 14:17:25 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:25 Arch-PC systemd[1]: geoclue.service: Succeeded.
mai 14 14:17:25 Arch-PC kernel: audit: type=1131 audit(1589476645.975:96): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:33 Arch-PC systemd[990]: tracker-extract.service: Succeeded.
mai 14 14:17:35 Arch-PC systemd[1]: systemd-hostnamed.service: Succeeded.
mai 14 14:17:35 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:35 Arch-PC kernel: audit: type=1131 audit(1589476655.625:97): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:35 Arch-PC audit: AUDIT1334 prog-id=18 op=UNLOAD
mai 14 14:17:35 Arch-PC audit: AUDIT1334 prog-id=17 op=UNLOAD
mai 14 14:17:35 Arch-PC kernel: audit: type=1334 audit(1589476655.655:98): prog-id=18 op=UNLOAD
mai 14 14:17:35 Arch-PC kernel: audit: type=1334 audit(1589476655.655:99): prog-id=17 op=UNLOAD
mai 14 14:17:52 Arch-PC systemd[1]: systemd-localed.service: Succeeded.
mai 14 14:17:52 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:52 Arch-PC kernel: audit: type=1131 audit(1589476672.872:100): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:17:52 Arch-PC audit: AUDIT1334 prog-id=14 op=UNLOAD
mai 14 14:17:52 Arch-PC audit: AUDIT1334 prog-id=13 op=UNLOAD
mai 14 14:17:52 Arch-PC kernel: audit: type=1334 audit(1589476672.929:101): prog-id=14 op=UNLOAD
mai 14 14:17:52 Arch-PC kernel: audit: type=1334 audit(1589476672.929:102): prog-id=13 op=UNLOAD
mai 14 14:17:53 Arch-PC tracker-store[1320]: OK
mai 14 14:17:53 Arch-PC systemd[990]: tracker-store.service: Succeeded.
mai 14 14:18:30 Arch-PC gnome-shell[1073]: JS ERROR: TypeError: database.start_refresh_tmp_files_dbs is not a function
_checkUpdatesEnd@/usr/share/gnome-shell/extensions/pamac-updates@manjaro.org/extension.js:331:13
wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
_checkUpdatesRead@/usr/share/gnome-shell/extensions/pamac-updates@manjaro.org/extension.js:316:8
wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
_checkUpdates/this._updateProcess_sourceId<@/usr/share/gnome-shell/extensions/pamac-updates@manjaro.org/extension.js:284:97
mai 14 14:21:08 Arch-PC systemd[990]: Started Application launched by gnome-shell.
mai 14 14:21:09 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.70' (uid=1003 pid=1665 comm="gnome-terminal ")
mai 14 14:21:09 Arch-PC systemd[990]: Created slice apps.slice.
mai 14 14:21:09 Arch-PC systemd[990]: Created slice apps-org.gnome.Terminal.slice.
mai 14 14:21:09 Arch-PC systemd[990]: Starting GNOME Terminal Server...
mai 14 14:21:10 Arch-PC gnome-terminal-server[1671]: Display does not support owner-change; copy/paste will be broken!
mai 14 14:21:10 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.gnome.Terminal'
mai 14 14:21:10 Arch-PC systemd[990]: Started GNOME Terminal Server.
mai 14 14:21:10 Arch-PC systemd[990]: Started VTE child process 1677 launched by gnome-terminal-server process 1671.
mai 14 14:21:10 Arch-PC systemd[990]: gnome-launched-org.gnome.Terminal.desktop-1665.scope: Succeeded.
mai 14 14:21:49 Arch-PC PackageKit[805]: daemon quit
mai 14 14:21:49 Arch-PC systemd[1]: packagekit.service: Succeeded.
mai 14 14:21:49 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:21:49 Arch-PC kernel: audit: type=1131 audit(1589476909.989:103): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:22:25 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.57' (uid=1003 pid=1229 comm="/usr/lib/tracker-miner-fs ")
mai 14 14:22:25 Arch-PC dbus-daemon[1028]: [session uid=1003 pid=1028] Successfully activated service 'org.freedesktop.Tracker1'
mai 14 14:22:25 Arch-PC systemd[990]: Starting Tracker metadata database store and lookup manager...
mai 14 14:22:25 Arch-PC systemd[990]: Started Tracker metadata database store and lookup manager.
mai 14 14:22:25 Arch-PC systemd[990]: gnome-terminal-server.service: Succeeded.
mai 14 14:22:56 Arch-PC tracker-store[1728]: OK
mai 14 14:22:56 Arch-PC systemd[990]: tracker-store.service: Succeeded.
mai 14 14:23:45 Arch-PC nautilus[1466]: ../gtk/gdk/wayland/gdkselection-wayland.c:280: error reading selection buffer: A operação foi cancelada
mai 14 14:30:48 Arch-PC systemd[1]: Starting Cleanup of Temporary Directories...
mai 14 14:30:51 Arch-PC systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
mai 14 14:30:51 Arch-PC systemd[1]: Finished Cleanup of Temporary Directories.
mai 14 14:30:51 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:30:51 Arch-PC kernel: audit: type=1130 audit(1589477451.445:104): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:30:51 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:30:51 Arch-PC kernel: audit: type=1131 audit(1589477451.449:105): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC gnome-shell[1073]: JS WARNING: [resource:///org/gnome/shell/ui/popupMenu.js 776]: reference to undefined property "_delegate"
mai 14 14:33:15 Arch-PC audit[1934]: USER_AUTH pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:15 Arch-PC kernel: audit: type=1100 audit(1589477595.805:106): pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:15 Arch-PC audit[1934]: USER_ACCT pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:15 Arch-PC audit[1934]: CRED_ACQ pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:15 Arch-PC kernel: audit: type=1101 audit(1589477595.809:107): pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:15 Arch-PC kernel: audit: type=1103 audit(1589477595.809:108): pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:15 Arch-PC systemd[1]: Created slice User Slice of UID 120.
mai 14 14:33:15 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/120...
mai 14 14:33:15 Arch-PC systemd-logind[499]: New session c2 of user gdm.
mai 14 14:33:15 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/120.
mai 14 14:33:15 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC kernel: audit: type=1130 audit(1589477595.852:109): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC systemd[1]: Starting User Manager for UID 120...
mai 14 14:33:15 Arch-PC audit[1941]: USER_ACCT pid=1941 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC systemd[1941]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:33:15 Arch-PC audit[1941]: CRED_ACQ pid=1941 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:33:15 Arch-PC kernel: audit: type=1101 audit(1589477595.862:110): pid=1941 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC kernel: audit: type=1103 audit(1589477595.862:111): pid=1941 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:33:15 Arch-PC kernel: audit: type=1006 audit(1589477595.862:112): pid=1941 uid=0 old-auid=4294967295 auid=120 tty=(none) old-ses=4294967295 ses=4 res=1
mai 14 14:33:15 Arch-PC systemd[1941]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
mai 14 14:33:15 Arch-PC audit[1941]: USER_START pid=1941 uid=0 auid=120 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC kernel: audit: type=1105 audit(1589477595.865:113): pid=1941 uid=0 auid=120 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC audit: AUDIT1334 prog-id=22 op=LOAD
mai 14 14:33:15 Arch-PC audit: AUDIT1334 prog-id=22 op=UNLOAD
mai 14 14:33:15 Arch-PC kernel: audit: type=1334 audit(1589477595.872:114): prog-id=22 op=LOAD
mai 14 14:33:15 Arch-PC kernel: audit: type=1334 audit(1589477595.872:115): prog-id=22 op=UNLOAD
mai 14 14:33:15 Arch-PC rtkit-daemon[800]: Supervising 2 threads of 1 processes of 1 users.
mai 14 14:33:15 Arch-PC rtkit-daemon[800]: Successfully made thread 1943 of process 1057 owned by '1003' RT at priority 5.
mai 14 14:33:15 Arch-PC rtkit-daemon[800]: Supervising 3 threads of 1 processes of 1 users.
mai 14 14:33:15 Arch-PC systemd[1941]: Reached target Paths.
mai 14 14:33:15 Arch-PC systemd[1941]: Reached target Timers.
mai 14 14:33:15 Arch-PC systemd[1941]: Starting D-Bus User Message Bus Socket.
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on GnuPG network certificate management daemon.
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on p11-kit server.
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on Multimedia System.
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on Sound System.
mai 14 14:33:15 Arch-PC systemd[1941]: Listening on D-Bus User Message Bus Socket.
mai 14 14:33:15 Arch-PC systemd[1941]: Reached target Sockets.
mai 14 14:33:15 Arch-PC systemd[1941]: Reached target Basic System.
mai 14 14:33:15 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:15 Arch-PC systemd[1]: Started User Manager for UID 120.
mai 14 14:33:15 Arch-PC systemd[1]: Started Session c2 of user gdm.
mai 14 14:33:15 Arch-PC systemd[1941]: Starting Update XDG user dir configuration...
mai 14 14:33:15 Arch-PC systemd[1941]: xdg-user-dirs-update.service: Succeeded.
mai 14 14:33:15 Arch-PC systemd[1941]: Finished Update XDG user dir configuration.
mai 14 14:33:15 Arch-PC systemd[1941]: Reached target Main User Target.
mai 14 14:33:15 Arch-PC systemd[1941]: Startup finished in 110ms.
mai 14 14:33:15 Arch-PC audit[1934]: USER_START pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:33:16 Arch-PC systemd[1941]: Started D-Bus User Message Bus.
mai 14 14:33:16 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:33:16 Arch-PC dbus-daemon[1955]: [session uid=120 pid=1955] Successfully activated service 'org.freedesktop.systemd1'
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC gnome-session[1959]: gnome-session-binary[1959]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC gnome-session-binary[1959]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC gnome-session[1959]: gnome-session-binary[1959]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
mai 14 14:33:16 Arch-PC gnome-session-binary[1959]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1959 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:16 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Successfully activated service 'org.a11y.Bus'
mai 14 14:33:16 Arch-PC org.gnome.Shell.desktop[2008]: glamor: No eglstream capable devices found
mai 14 14:33:17 Arch-PC gnome-shell[1975]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mai 14 14:33:17 Arch-PC gnome-shell[1975]: Will monitor session c2
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.124' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC audit: AUDIT1334 prog-id=23 op=LOAD
mai 14 14:33:17 Arch-PC audit: AUDIT1334 prog-id=24 op=LOAD
mai 14 14:33:17 Arch-PC systemd[1]: Starting Locale Service...
mai 14 14:33:17 Arch-PC gnome-shell[1975]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='ca.desrt.dconf' requested by ':1.3' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Successfully activated service 'ca.desrt.dconf'
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
mai 14 14:33:17 Arch-PC systemd[1941]: Starting Sound Service...
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.124' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Starting Location Lookup Service...
mai 14 14:33:17 Arch-PC polkitd[535]: Registered Authentication Agent for unix-session:c2 (system bus name :1.124 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.124' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:33:17 Arch-PC systemd[1]: Starting PackageKit Daemon...
mai 14 14:33:17 Arch-PC PackageKit[2026]: daemon start
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
mai 14 14:33:17 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:17 Arch-PC systemd[1]: Started Location Lookup Service.
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.126' (uid=967 pid=2025 comm="/usr/lib/geoclue ")
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 14 14:33:17 Arch-PC geoclue[2025]: Failed to connect to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.PackageKit'
mai 14 14:33:17 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:17 Arch-PC systemd[1]: Started PackageKit Daemon.
mai 14 14:33:17 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.locale1'
mai 14 14:33:17 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:17 Arch-PC systemd[1]: Started Locale Service.
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[2005]: dbus-daemon[2005]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[2005]: dbus-daemon[2005]: Successfully activated service 'org.a11y.atspi.Registry'
mai 14 14:33:17 Arch-PC /usr/lib/gdm-wayland-session[2036]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
mai 14 14:33:17 Arch-PC gnome-shell[1975]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Successfully made thread 2024 of process 2024 owned by '120' high priority at nice level -11.
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:33:18 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.130' (uid=120 pid=2053 comm="/usr/lib/gsd-rfkill ")
mai 14 14:33:18 Arch-PC audit: AUDIT1334 prog-id=25 op=LOAD
mai 14 14:33:18 Arch-PC audit: AUDIT1334 prog-id=26 op=LOAD
mai 14 14:33:18 Arch-PC systemd[1]: Starting Hostname Service...
mai 14 14:33:18 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.10' (uid=120 pid=2042 comm="/usr/lib/gsd-sharing ")
mai 14 14:33:18 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:18 Arch-PC gsd-sharing[2042]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:18 Arch-PC gsd-sharing[2042]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:18 Arch-PC gsd-sharing[2042]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Successfully made thread 2113 of process 2024 owned by '120' RT at priority 5.
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Successfully made thread 2123 of process 2024 owned by '120' RT at priority 5.
mai 14 14:33:18 Arch-PC rtkit-daemon[800]: Supervising 6 threads of 2 processes of 2 users.
mai 14 14:33:18 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.135' (uid=120 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no ")
mai 14 14:33:18 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
mai 14 14:33:18 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Successfully activated service 'org.gnome.Shell.Notifications'
mai 14 14:33:18 Arch-PC systemd[1941]: Started Sound Service.
mai 14 14:33:18 Arch-PC pulseaudio[2024]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2154]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2154]: > Internal error: Could not resolve keysym XF86FullScreen
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2154]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:18 Arch-PC gnome-shell[1975]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:18 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.3' (uid=120 pid=1975 comm="/usr/bin/gnome-shell ")
mai 14 14:33:18 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:18 Arch-PC gnome-shell[1975]: Could not issue 'StartUnit' systemd call
mai 14 14:33:18 Arch-PC dbus-daemon[494]: [system] Successfully activated service 'org.freedesktop.hostname1'
mai 14 14:33:18 Arch-PC systemd[1]: Started Hostname Service.
mai 14 14:33:18 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:18 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2157]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2157]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2157]: > X11 cannot support keycodes above 255.
mai 14 14:33:18 Arch-PC org.gnome.Shell.desktop[2157]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:18 Arch-PC gnome-shell[1073]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:33:18 Arch-PC gnome-session-binary[1959]: Entering running state
mai 14 14:33:18 Arch-PC xbrlapi.desktop[2167]: openConnection: connect: Arquivo ou diretório inexistente
mai 14 14:33:18 Arch-PC xbrlapi.desktop[2167]: cannot connect to braille devices daemon brltty at :0
mai 14 14:33:18 Arch-PC gsd-media-keys[2058]: Failed to grab accelerator for keybinding settings:playback-random
mai 14 14:33:18 Arch-PC gsd-media-keys[2058]: Failed to grab accelerator for keybinding settings:hibernate
mai 14 14:33:18 Arch-PC gsd-media-keys[2058]: Failed to grab accelerator for keybinding settings:playback-repeat
mai 14 14:33:18 Arch-PC gsd-media-keys[2058]: Failed to grab accelerator for keybinding settings:rfkill
mai 14 14:33:19 Arch-PC gnome-shell[1975]: Registering session with GDM
mai 14 14:33:21 Arch-PC gdm-password][2170]: gkr-pam: unlocked login keyring
mai 14 14:33:21 Arch-PC audit[2170]: USER_AUTH pid=2170 uid=0 auid=1003 ses=2 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:21 Arch-PC kernel: kauditd_printk_skb: 10 callbacks suppressed
mai 14 14:33:21 Arch-PC kernel: audit: type=1100 audit(1589477601.689:126): pid=2170 uid=0 auid=1003 ses=2 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:21 Arch-PC audit[2170]: USER_ACCT pid=2170 uid=0 auid=1003 ses=2 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:21 Arch-PC kernel: audit: type=1101 audit(1589477601.722:127): pid=2170 uid=0 auid=1003 ses=2 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:21 Arch-PC audit[2170]: CRED_REFR pid=2170 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:21 Arch-PC kernel: audit: type=1110 audit(1589477601.725:128): pid=2170 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:22 Arch-PC gnome-shell[2182]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:22 Arch-PC gnome-shell[2182]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:33:22 Arch-PC gnome-shell[2182]: > X11 cannot support keycodes above 255.
mai 14 14:33:22 Arch-PC gnome-shell[2182]: > Internal error: Could not resolve keysym Invalid
mai 14 14:33:22 Arch-PC gnome-shell[2182]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:22 Arch-PC NetworkManager[495]: <info> [1589477602.5125] agent-manager: agent[cfa9daec80ad46cc,:1.59/org.gnome.Shell.NetworkAgent/1003]: agent registered
mai 14 14:33:23 Arch-PC gnome-shell[1975]: Warning: Failed to start gsd-xsettings
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Date & Time handling.
mai 14 14:33:28 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:28 Arch-PC systemd[990]: gsd-rfkill.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped GNOME RFKill handling.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-usb-protection.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-screensaver-proxy.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-sound.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-a11y-settings.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-datetime.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped GNOME Date & Time handling.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-housekeeping.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-print-notifications.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-sharing.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped GNOME Sharing handling.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-smartcard.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: gsd-wwan.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: at-spi-dbus-bus.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Accessibility settings.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Maintenance of expirable data.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Printer notifications.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME RFKill handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Freedesktop screensaver handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Sharing handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Smartcard handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Sound sample caching handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME USB protection handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME WWan management.
mai 14 14:33:28 Arch-PC systemd[990]: Stopping GNOME XSettings...
mai 14 14:33:28 Arch-PC systemd[990]: gsd-xsettings.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped GNOME XSettings.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Wayland Session (session: gnome).
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target Current graphical user session.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Session.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Wayland Session.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Session (session: gnome).
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Color management.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Keyboard handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Media keys handling.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Power management handling.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC tracker-miner-fs.desktop[1229]: Received signal:15->'Terminado'
mai 14 14:33:28 Arch-PC systemd[990]: Stopped target GNOME Wacom handling.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC systemd[990]: Stopping GNOME Color management...
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC systemd[990]: Stopping GNOME Keyboard handling...
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC systemd[990]: Stopping GNOME Media keys handling...
mai 14 14:33:28 Arch-PC systemd[990]: Stopping GNOME Power management handling...
mai 14 14:33:28 Arch-PC systemd[990]: Stopping GNOME Wacom handling...
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfea63060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfea6d040.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfea6d040.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfea6e770.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfea63060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfea75100.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfea75100.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfea76cd0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfea63060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfbf94f90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf9dab0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf9dab0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbf9f2d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfbf94f90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbfa5cb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbfa5cb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbfa74a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfbf94f90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfea46000.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfea46000.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfea47850.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfbf94f90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfbf62880.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC tracker-miner-fs.desktop[1229]: OK
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf6a8f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf6a8f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbf6c900.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfbf62880.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf72700.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf72700.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbf76470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfbf62880.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf7c5d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbf7c5d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbf7d7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfbf62880.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfddaba00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddb41c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddb41c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfddb5d00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfddaba00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddbc5c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddbc5c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfddbd910.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfddaba00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddc3fd0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddc3fd0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfddc65a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfddaba00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddcc0f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfddcc0f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfddce500.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfddaba00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfd3888d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfde7a090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfde7a090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfde7b470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfd3888d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfde7f560.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfde7f560.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfde80900.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfd3888d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd1d940.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd1d940.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbd1f480.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfd3888d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd25890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd25890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfdd92e50.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfd3888d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfb9a09b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb9b1820.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb9b1820.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb9b2ac0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfb9a09b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb9a9690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb9a9690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb9ab1d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfb9a09b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd26af0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd26af0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbd28380.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfb9a09b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd0ea40.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd0ea40.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbd10fd0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfb9a09b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc61a890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc61a890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc61c2b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc622eb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc622eb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc6241e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc62a880.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc62a880.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc62d030.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfba35590.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfba35590.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfba370d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfba3e090.
mai 14 14:33:28 Arch-PC systemd[990]: gnome-session-manager@gnome.service: Succeeded.
mai 14 14:33:28 Arch-PC systemd[990]: Stopped GNOME Session Manager (session: gnome).
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfba3e090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfba3f140.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4d9530.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4d9530.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb4dada0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4e0e80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4e0e80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb4e26e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4e8ef0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4e8ef0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb4ea680.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb8625b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb8625b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb8636f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb854600.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb854600.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb8569a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb85cdc0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb85cdc0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb85e940.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564c00144930.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564c00144930.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564c00145c60.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564c0014c4f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564c0014c4f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564c0014e0d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb44840.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb44840.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfefe08d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfefe6d20.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfefe6d20.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfefe88d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfefef860.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfefef860.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeff1490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfba1f7c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb97c920.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb97c920.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd1f0bf0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd1f7c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd1f7c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd1f8a00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb7f2400.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb7f2400.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb40f10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebd2090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebd2090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfebd3b40.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfead9490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfead9490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeadb090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb5a42e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb5a42e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb5a5a70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb898db0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb898db0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb89adb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec2c870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec2c870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec5a870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebc8390.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebc8390.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeafbf00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bff204970.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bff204970.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bff5d1d90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe7a9890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe7a9890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe780af0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb45160.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb45160.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb8aa800.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb84f490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb84f490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc6545a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbabb060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbabb060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbabc3a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe8a8c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe8a8c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe5c2510.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfdcc7c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfdcc7c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe5a5da0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe71ca90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe71ca90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc713c00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6f3a90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6f3a90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe685470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd5567c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd5567c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bffbe60d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb833c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb833c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb8357b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfba8bcf0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfba8bcf0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfba8d870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd559c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd559c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd55b630.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6b99f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6b99f0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe891c70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeae8f10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeae8f10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd59bc70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebdb890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebdb890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfebdcc00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb90890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb90890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb924a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeba0c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeba0c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeba2580.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb92f430.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb92f430.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb930f90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb75d950.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb75d950.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bff5a4010.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb273a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb273a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb28170.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe71f490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe71f490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe735870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe697690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe697690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb8f2d50.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd3aa00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbd3aa00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfdcc07e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe7262e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe7262e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe689870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bff5c3230.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bff5c3230.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe89b270.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec086d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec086d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec35870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec205e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec205e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec22460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb94c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb94c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb95c80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb5ac090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb5ac090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb5eb870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec1d010.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec1d010.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec1e820.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb64f60.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb64f60.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb95cec0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeba8090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeba8090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc6614d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd54ec90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd54ec90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd54fcd0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb920160.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb920160.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb921ef0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb603c10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb603c10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb604f50.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564c0013b090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564c0013b090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564c0013c430.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeadb6a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeadb6a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeab4510.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb69ad30.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb69ad30.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb4fc660.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb974b70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb974b70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb976740.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb7bcee0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb7bcee0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec71060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb30490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb30490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb319d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe844e90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe844e90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe713790.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebdf870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebdf870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfebe10a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbb289b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbb289b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe83fc70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec4b430.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec4b430.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec4cff0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb5c4c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb5c4c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfc63c4e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe887890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe887890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe7e8d70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd0d7090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd0d7090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfba78070.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbb02530.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfbb02530.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbb04020.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe89f690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe89f690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe83b870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfde53850.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfde53850.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe6ea470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb8a690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb8a690.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb8c240.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd55ecb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfd55ecb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd55fc30.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4d7a80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4d7a80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb919a70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe5a3c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe5a3c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec2ad60.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeaf5090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeaf5090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd3a76d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe749e90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe749e90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe7b2e70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb7a8f80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb7a8f80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeab6470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebb3c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebb3c90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfebb4d90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebeac90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebeac90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec3efb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb942290.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb942290.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb943e80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebf4480.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebf4480.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfebbdb30.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeaaceb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeaaceb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeaaedd0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb937490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb937490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb9386d0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfdca8220.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfdca8220.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfd3ffc70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb1d890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb1d890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec3a870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe7f3e90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe7f3e90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe7f5870.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe738300.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe738300.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb7d1910.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe5ac420.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe5ac420.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfbacbdb0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc910d40.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfc910d40.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe720e70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe8d1e70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe8d1e70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe800a70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb389e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb389e0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb3a6b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec26a30.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfec26a30.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfec41de0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb871a90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb871a90.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb873680.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb5f2210.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb5f2210.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb5f6470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebc2b20.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfebc2b20.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfebf7470.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb9b2c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfeb9b2c0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfeb9cb50.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4cf130.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb4cf130.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb4d1560.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb909d70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb909d70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb90ee20.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe59b6b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe59b6b0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe59ce80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb692dc0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb692dc0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb694d00.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb502b10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb502b10.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: == Stack trace for context 0x564bfb1a4480 ==
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb503ee0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfdc90060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfdc90060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfdc91d20.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb8901a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfb8901a0.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfb891a80.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe85a460.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfe783260.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6b7090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6b7090.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe7e1e70.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe783260.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x564bfe749060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe878490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe878490.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe6fe070.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe749060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6d7890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564bfe6d7890.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564bfe8a2070.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x564bfe749060.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was notify on NMDeviceEthernet 0x564bfdd40230.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was notify on NMActiveConnection 0x564bfdd43180.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was notify on NMActiveConnection 0x564bfdd43180.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:33:28 Arch-PC gnome-shell[1073]: The offending signal was state-changed on NMDeviceEthernet 0x564bfdd40230.
mai 14 14:33:29 Arch-PC systemd[990]: gsd-keyboard.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped GNOME Keyboard handling.
mai 14 14:33:29 Arch-PC gnome-shell[1105]: (EE) failed to read Wayland events: Broken pipe
mai 14 14:33:29 Arch-PC systemd[990]: gsd-wacom.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped GNOME Wacom handling.
mai 14 14:33:29 Arch-PC systemd[990]: gsd-media-keys.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped GNOME Media keys handling.
mai 14 14:33:29 Arch-PC polkitd[535]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.59, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus)
mai 14 14:33:29 Arch-PC systemd[990]: gsd-power.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped GNOME Power management handling.
mai 14 14:33:29 Arch-PC systemd[990]: gsd-color.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped GNOME Color management.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target GNOME Session is initialized.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target GNOME Shell on Wayland.
mai 14 14:33:29 Arch-PC gsd-color[2048]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Electronics_23MP55_16843009_stalker_1003
mai 14 14:33:29 Arch-PC gnome-shell[1975]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:33:29 Arch-PC systemd[990]: gnome-shell-wayland.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped GNOME Shell on Wayland.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target GNOME Session Manager is ready.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target Tasks to be run before GNOME Session starts.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target Session services which should run early before the graphical session is brought up.
mai 14 14:33:29 Arch-PC systemd[990]: Reached target Shutdown running GNOME Session.
mai 14 14:33:29 Arch-PC systemd[990]: Stopping Monitor Session leader for GNOME Session...
mai 14 14:33:29 Arch-PC systemd[990]: Starting Restart DBus after GNOME Session shutdown...
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target Shutdown running GNOME Session.
mai 14 14:33:29 Arch-PC systemd[990]: Reached target Shutdown running GNOME Session.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped target Shutdown running GNOME Session.
mai 14 14:33:29 Arch-PC gdm-password][948]: pam_unix(gdm-password:session): session closed for user stalker
mai 14 14:33:29 Arch-PC systemd[990]: Started Restart DBus after GNOME Session shutdown.
mai 14 14:33:29 Arch-PC systemd[990]: gnome-session-monitor.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped Monitor Session leader for GNOME Session.
mai 14 14:33:29 Arch-PC audit[948]: USER_END pid=948 uid=0 auid=1003 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:33:29 Arch-PC audit[948]: USER_LOGOUT pid=948 uid=0 auid=1003 ses=2 msg='uid=1003 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:33:29 Arch-PC audit[948]: CRED_DISP pid=948 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:33:29 Arch-PC kernel: audit: type=1106 audit(1589477609.112:129): pid=948 uid=0 auid=1003 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:33:29 Arch-PC kernel: audit: type=1113 audit(1589477609.112:130): pid=948 uid=0 auid=1003 ses=2 msg='uid=1003 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:33:29 Arch-PC kernel: audit: type=1104 audit(1589477609.112:131): pid=948 uid=0 auid=1003 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="stalker" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:33:29 Arch-PC gvfsd[1125]: A connection to the bus can't be made
mai 14 14:33:29 Arch-PC systemd[990]: Stopping D-Bus User Message Bus...
mai 14 14:33:29 Arch-PC systemd[1941]: run-user-1003-gvfs.mount: Succeeded.
mai 14 14:33:29 Arch-PC systemd[1]: run-user-1003-gvfs.mount: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: run-user-1003-gvfs.mount: Succeeded.
mai 14 14:33:29 Arch-PC pulseaudio[1057]: E: [pulseaudio] stdin-util.c: Unable to read or parse data from client.
mai 14 14:33:29 Arch-PC evolution-calen[1201]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: A conexão está fechada (g-io-error-quark, 18)
mai 14 14:33:29 Arch-PC evolution-calen[1201]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: A conexão está fechada (g-io-error-quark, 18)
mai 14 14:33:29 Arch-PC evolution-addre[1395]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: A conexão está fechada (g-io-error-quark, 18)
mai 14 14:33:29 Arch-PC systemd[990]: evolution-addressbook-factory.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: evolution-source-registry.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
mai 14 14:33:29 Arch-PC systemd[990]: xdg-permission-store.service: Failed with result 'exit-code'.
mai 14 14:33:29 Arch-PC systemd[990]: pulseaudio.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: evolution-calendar-factory.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: gvfs-metadata.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: gnome-session-restart-dbus.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: dbus.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Stopped D-Bus User Message Bus.
mai 14 14:33:29 Arch-PC systemd[990]: gvfs-daemon.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[990]: Started D-Bus User Message Bus.
mai 14 14:33:29 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:33:29 Arch-PC systemd[990]: gvfs-udisks2-volume-monitor.service: Succeeded.
mai 14 14:33:29 Arch-PC systemd[1]: session-2.scope: Succeeded.
mai 14 14:33:29 Arch-PC systemd-logind[499]: Session 2 logged out. Waiting for processes to exit.
mai 14 14:33:29 Arch-PC systemd-logind[499]: Removed session 2.
mai 14 14:33:29 Arch-PC org.gnome.Shell.desktop[2206]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:29 Arch-PC org.gnome.Shell.desktop[2206]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:33:29 Arch-PC org.gnome.Shell.desktop[2206]: > X11 cannot support keycodes above 255.
mai 14 14:33:29 Arch-PC org.gnome.Shell.desktop[2206]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:29 Arch-PC gnome-shell[1975]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
mai 14 14:33:38 Arch-PC gdm-password][2215]: gkr-pam: unable to locate daemon control file
mai 14 14:33:38 Arch-PC audit[2215]: USER_AUTH pid=2215 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:38 Arch-PC gdm-password][2215]: gkr-pam: stashed password to try later in open session
mai 14 14:33:38 Arch-PC kernel: audit: type=1100 audit(1589477618.652:132): pid=2215 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:38 Arch-PC audit[2215]: USER_ACCT pid=2215 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:38 Arch-PC kernel: audit: type=1101 audit(1589477618.682:133): pid=2215 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:38 Arch-PC audit[2215]: CRED_ACQ pid=2215 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:38 Arch-PC kernel: audit: type=1103 audit(1589477618.702:134): pid=2215 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:38 Arch-PC kernel: audit: type=1006 audit(1589477618.782:135): pid=2215 uid=0 old-auid=4294967295 auid=1004 tty=(none) old-ses=4294967295 ses=5 res=1
mai 14 14:33:38 Arch-PC gdm-password][2215]: pam_unix(gdm-password:session): session opened for user xanadu by (uid=0)
mai 14 14:33:38 Arch-PC systemd[1]: Created slice User Slice of UID 1004.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:33:38 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/1004...
mai 14 14:33:38 Arch-PC systemd-logind[499]: New session 5 of user xanadu.
mai 14 14:33:38 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/1004.
mai 14 14:33:38 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC systemd[1]: Starting User Manager for UID 1004...
mai 14 14:33:38 Arch-PC kernel: audit: type=1130 audit(1589477618.822:136): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC audit[2223]: USER_ACCT pid=2223 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC systemd[2223]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[xanadu] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:33:38 Arch-PC audit[2223]: CRED_ACQ pid=2223 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:33:38 Arch-PC kernel: audit: type=1101 audit(1589477618.829:137): pid=2223 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC kernel: audit: type=1103 audit(1589477618.829:138): pid=2223 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:33:38 Arch-PC kernel: audit: type=1006 audit(1589477618.829:139): pid=2223 uid=0 old-auid=4294967295 auid=1004 tty=(none) old-ses=4294967295 ses=6 res=1
mai 14 14:33:38 Arch-PC systemd[2223]: pam_unix(systemd-user:session): session opened for user xanadu by (uid=0)
mai 14 14:33:38 Arch-PC audit[2223]: USER_START pid=2223 uid=0 auid=1004 ses=6 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC kernel: audit: type=1105 audit(1589477618.832:140): pid=2223 uid=0 auid=1004 ses=6 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC audit: AUDIT1334 prog-id=27 op=LOAD
mai 14 14:33:38 Arch-PC audit: AUDIT1334 prog-id=27 op=UNLOAD
mai 14 14:33:38 Arch-PC kernel: audit: type=1334 audit(1589477618.839:141): prog-id=27 op=LOAD
mai 14 14:33:38 Arch-PC systemd[2223]: Reached target Paths.
mai 14 14:33:38 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC audit[2215]: USER_START pid=2215 uid=0 auid=1004 ses=5 msg='op=PAM:session_open grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:33:38 Arch-PC audit[2215]: USER_LOGIN pid=2215 uid=0 auid=1004 ses=5 msg='uid=1004 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:33:38 Arch-PC gdm-password][2215]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
mai 14 14:33:38 Arch-PC systemd[2223]: Reached target Timers.
mai 14 14:33:38 Arch-PC systemd[2223]: Starting D-Bus User Message Bus Socket.
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on GnuPG network certificate management daemon.
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on p11-kit server.
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on Multimedia System.
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on Sound System.
mai 14 14:33:38 Arch-PC systemd[2223]: Listening on D-Bus User Message Bus Socket.
mai 14 14:33:38 Arch-PC systemd[2223]: Reached target Sockets.
mai 14 14:33:38 Arch-PC systemd[2223]: Reached target Basic System.
mai 14 14:33:38 Arch-PC systemd[1]: Started User Manager for UID 1004.
mai 14 14:33:38 Arch-PC systemd[1]: Started Session 5 of user xanadu.
mai 14 14:33:38 Arch-PC systemd[2223]: Starting Update XDG user dir configuration...
mai 14 14:33:38 Arch-PC systemd[2223]: xdg-user-dirs-update.service: Succeeded.
mai 14 14:33:38 Arch-PC systemd[2223]: Finished Update XDG user dir configuration.
mai 14 14:33:38 Arch-PC systemd[2223]: Reached target Main User Target.
mai 14 14:33:38 Arch-PC systemd[2223]: Startup finished in 120ms.
mai 14 14:33:39 Arch-PC systemd[2223]: Started D-Bus User Message Bus.
mai 14 14:33:39 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session-pre.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session-initialized.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session@gnome-initial-setup.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session@gnome-login.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session-failed.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session-wayland.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: gnome-session@gnome.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
mai 14 14:33:39 Arch-PC systemd[2223]: Created slice gnome\x2dsession\x2dmanager.slice.
mai 14 14:33:39 Arch-PC systemd[2223]: Reached target Session services which should run early before the graphical session is brought up.
mai 14 14:33:39 Arch-PC systemd[2223]: Starting Monitor Session leader for GNOME Session...
mai 14 14:33:39 Arch-PC gnome-session-c[2269]: Error creating FIFO: Arquivo existe
mai 14 14:33:39 Arch-PC systemd[2223]: Starting Sound Service...
mai 14 14:33:39 Arch-PC systemd[2223]: Started Monitor Session leader for GNOME Session.
mai 14 14:33:39 Arch-PC systemd[2223]: Reached target Tasks to be run before GNOME Session starts.
mai 14 14:33:39 Arch-PC systemd[2223]: Starting GNOME Session Manager (session: gnome)...
mai 14 14:33:39 Arch-PC gnome-session[2272]: gnome-session-binary[2272]: WARNING: Could not parse desktop file kaccess.desktop or it references a not found TryExec binary
mai 14 14:33:39 Arch-PC gnome-session-binary[2272]: WARNING: Could not parse desktop file kaccess.desktop or it references a not found TryExec binary
mai 14 14:33:39 Arch-PC gnome-session[2272]: gnome-session-binary[2272]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
mai 14 14:33:39 Arch-PC gnome-session-binary[2272]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
mai 14 14:33:39 Arch-PC gnome-keyring-ssh.desktop[2287]: SSH_AUTH_SOCK=/run/user/1004/keyring/ssh
mai 14 14:33:39 Arch-PC gnome-keyring-pkcs11.desktop[2288]: SSH_AUTH_SOCK=/run/user/1004/keyring/ssh
mai 14 14:33:39 Arch-PC systemd[2223]: Started GNOME Session Manager (session: gnome).
mai 14 14:33:39 Arch-PC systemd[2223]: Reached target GNOME Session Manager is ready.
mai 14 14:33:39 Arch-PC systemd[2223]: Starting GNOME Shell on Wayland...
mai 14 14:33:39 Arch-PC systemd[1]: Stopping User Manager for UID 1003...
mai 14 14:33:39 Arch-PC systemd[990]: vte-spawn-2e84ae5b-0bf8-4542-b527-8425f621d820.scope: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped VTE child process 1677 launched by gnome-terminal-server process 1671.
mai 14 14:33:39 Arch-PC systemd[990]: Removed slice apps-org.gnome.Terminal.slice.
mai 14 14:33:39 Arch-PC systemd[990]: Removed slice apps.slice.
mai 14 14:33:39 Arch-PC systemd[990]: Removed slice gnome\x2dsession\x2dmanager.slice.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped target Main User Target.
mai 14 14:33:39 Arch-PC systemd[990]: Stopping D-Bus User Message Bus...
mai 14 14:33:39 Arch-PC systemd[990]: dbus.service: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped D-Bus User Message Bus.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped target Basic System.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped target Paths.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped target Sockets.
mai 14 14:33:39 Arch-PC systemd[990]: Stopped target Timers.
mai 14 14:33:39 Arch-PC systemd[990]: dbus.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed D-Bus User Message Bus Socket.
mai 14 14:33:39 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:39 Arch-PC systemd[990]: dirmngr.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed GnuPG network certificate management daemon.
mai 14 14:33:39 Arch-PC systemd[990]: gpg-agent-browser.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:33:39 Arch-PC systemd[990]: gpg-agent-extra.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:33:39 Arch-PC systemd[990]: gpg-agent-ssh.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:33:39 Arch-PC systemd[990]: gpg-agent.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed GnuPG cryptographic agent and passphrase cache.
mai 14 14:33:39 Arch-PC systemd[990]: p11-kit-server.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed p11-kit server.
mai 14 14:33:39 Arch-PC systemd[990]: pipewire.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed Multimedia System.
mai 14 14:33:39 Arch-PC systemd[990]: pulseaudio.socket: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Closed Sound System.
mai 14 14:33:39 Arch-PC systemd[990]: Reached target Shutdown.
mai 14 14:33:39 Arch-PC systemd[990]: systemd-exit.service: Succeeded.
mai 14 14:33:39 Arch-PC systemd[990]: Finished Exit the Session.
mai 14 14:33:39 Arch-PC systemd[990]: Reached target Exit the Session.
mai 14 14:33:39 Arch-PC systemd[1]: user@1003.service: Killing process 1680 (powerline-daemo) with signal SIGKILL.
mai 14 14:33:39 Arch-PC systemd[1]: user@1003.service: Succeeded.
mai 14 14:33:39 Arch-PC systemd[1]: Stopped User Manager for UID 1003.
mai 14 14:33:39 Arch-PC systemd[1]: Stopping User Runtime Directory /run/user/1003...
mai 14 14:33:39 Arch-PC systemd[1941]: run-user-1003.mount: Succeeded.
mai 14 14:33:39 Arch-PC systemd[1]: run-user-1003.mount: Succeeded.
mai 14 14:33:39 Arch-PC systemd[2223]: run-user-1003.mount: Succeeded.
mai 14 14:33:39 Arch-PC systemd[1]: user-runtime-dir@1003.service: Succeeded.
mai 14 14:33:39 Arch-PC systemd[1]: Stopped User Runtime Directory /run/user/1003.
mai 14 14:33:39 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:39 Arch-PC systemd[1]: Removed slice User Slice of UID 1003.
mai 14 14:33:39 Arch-PC rtkit-daemon[800]: Successfully made thread 2271 of process 2271 owned by '1004' high priority at nice level -11.
mai 14 14:33:39 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:33:40 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:33:40 Arch-PC rtkit-daemon[800]: Successfully made thread 2307 of process 2271 owned by '1004' RT at priority 5.
mai 14 14:33:40 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.10' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:40 Arch-PC systemd[2223]: Starting Accessibility services bus...
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.a11y.Bus'
mai 14 14:33:40 Arch-PC systemd[2223]: Started Accessibility services bus.
mai 14 14:33:40 Arch-PC gnome-shell[2317]: glamor: No eglstream capable devices found
mai 14 14:33:40 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:33:40 Arch-PC rtkit-daemon[800]: Successfully made thread 2322 of process 2271 owned by '1004' RT at priority 5.
mai 14 14:33:40 Arch-PC rtkit-daemon[800]: Supervising 6 threads of 2 processes of 2 users.
mai 14 14:33:40 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.157' (uid=1004 pid=2271 comm="/usr/bin/pulseaudio --daemonize=no ")
mai 14 14:33:40 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
mai 14 14:33:40 Arch-PC systemd[2223]: Started Sound Service.
mai 14 14:33:40 Arch-PC pulseaudio[2271]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
mai 14 14:33:40 Arch-PC gnome-shell[2289]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mai 14 14:33:40 Arch-PC gnome-shell[2289]: Will monitor session 5
mai 14 14:33:40 Arch-PC gnome-shell[2289]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating service name='ca.desrt.dconf' requested by ':1.8' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'ca.desrt.dconf'
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.8' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:40 Arch-PC systemd[2223]: Starting sandboxed app permission store...
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
mai 14 14:33:40 Arch-PC systemd[2223]: Started sandboxed app permission store.
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.8' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.15' (uid=1004 pid=2338 comm="/usr/lib/gnome-shell-calendar-server ")
mai 14 14:33:40 Arch-PC systemd[2223]: Starting Evolution source registry...
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.16' (uid=1004 pid=2342 comm="/usr/lib/evolution-source-registry ")
mai 14 14:33:40 Arch-PC systemd[2223]: Starting Virtual filesystem service...
mai 14 14:33:40 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gtk.vfs.Daemon'
mai 14 14:33:40 Arch-PC systemd[2223]: Started Virtual filesystem service.
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating service name='org.gnome.OnlineAccounts' requested by ':1.16' (uid=1004 pid=2342 comm="/usr/lib/evolution-source-registry ")
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
mai 14 14:33:41 Arch-PC systemd[2223]: Started Evolution source registry.
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.Shell.CalendarServer'
mai 14 14:33:41 Arch-PC polkitd[535]: Registered Authentication Agent for unix-session:5 (system bus name :1.153 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 14 14:33:41 Arch-PC gnome-shell[2289]: Telepathy is not available, chat integration will be disabled.
mai 14 14:33:41 Arch-PC goa-daemon[2361]: goa-daemon version 3.36.0 starting
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating service name='org.gnome.Identity' requested by ':1.19' (uid=1004 pid=2361 comm="/usr/lib/goa-daemon ")
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.8' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:41 Arch-PC systemd[2223]: Starting Virtual filesystem service - disk device monitor...
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.Identity'
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.OnlineAccounts'
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
mai 14 14:33:41 Arch-PC systemd[2223]: Started Virtual filesystem service - disk device monitor.
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating service name='org.gnome.Shell.Notifications' requested by ':1.8' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:41 Arch-PC at-spi-bus-launcher[2314]: dbus-daemon[2314]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1004 pid=2289 comm="/usr/bin/gnome-shell ")
mai 14 14:33:41 Arch-PC at-spi-bus-launcher[2314]: dbus-daemon[2314]: Successfully activated service 'org.a11y.atspi.Registry'
mai 14 14:33:41 Arch-PC at-spi-bus-launcher[2387]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.15' (uid=1004 pid=2338 comm="/usr/lib/gnome-shell-calendar-server ")
mai 14 14:33:41 Arch-PC systemd[2223]: Starting Evolution calendar service...
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Shell on Wayland.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Shell on Wayland.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Session is initialized.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Wayland Session.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Session (session: gnome).
mai 14 14:33:41 Arch-PC systemd[2223]: Starting Signal initialization done to GNOME Session Manager...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Accessibility settings...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Color management...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Date & Time handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Maintenance of expirable data...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Keyboard handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Media keys handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Power management handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Printer notifications...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME RFKill handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Freedesktop screensaver handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Sharing handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Smartcard handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Sound sample caching handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME USB protection handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME Wacom handling...
mai 14 14:33:41 Arch-PC systemd[2223]: Starting GNOME WWan management...
mai 14 14:33:41 Arch-PC gnome-shell[2289]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Accessibility settings.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Accessibility settings.
mai 14 14:33:41 Arch-PC NetworkManager[495]: <info> [1589477621.5710] agent-manager: agent[4c41b95ad2f791c6,:1.153/org.gnome.Shell.NetworkAgent/1004]: agent registered
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
mai 14 14:33:41 Arch-PC systemd[2223]: Started Evolution calendar service.
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.Shell.Notifications'
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.27' (uid=1004 pid=2394 comm="/usr/lib/evolution-calendar-factory ")
mai 14 14:33:41 Arch-PC systemd[2223]: Starting Evolution address book service...
mai 14 14:33:41 Arch-PC gnome-session-binary[2272]: Entering running state
mai 14 14:33:41 Arch-PC systemd[2223]: gnome-session-signal-init.service: Succeeded.
mai 14 14:33:41 Arch-PC systemd[2223]: Finished Signal initialization done to GNOME Session Manager.
mai 14 14:33:41 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Sharing handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Sharing handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME RFKill handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME RFKill handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Freedesktop screensaver handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Freedesktop screensaver handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Date & Time handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Date & Time handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME USB protection handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME USB protection handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Smartcard handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME WWan management.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Printer notifications.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Printer notifications.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Smartcard handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME WWan management.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Sound sample caching handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Sound sample caching handling.
mai 14 14:33:41 Arch-PC systemd[2223]: Started GNOME Maintenance of expirable data.
mai 14 14:33:41 Arch-PC systemd[2223]: Reached target GNOME Maintenance of expirable data.
mai 14 14:33:41 Arch-PC tracker-extract[2436]: Set scheduler policy to SCHED_IDLE
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.45' (uid=1004 pid=2478 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free")
mai 14 14:33:41 Arch-PC systemd[2223]: Starting Tracker metadata database store and lookup manager...
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
mai 14 14:33:41 Arch-PC systemd[2223]: Started Evolution address book service.
mai 14 14:33:41 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.freedesktop.Tracker1'
mai 14 14:33:41 Arch-PC systemd[2223]: Started Tracker metadata database store and lookup manager.
mai 14 14:33:41 Arch-PC tracker-store.desktop[2478]: (uint32 1,)
mai 14 14:33:41 Arch-PC tracker-miner-f[2427]: Set scheduler policy to SCHED_IDLE
mai 14 14:33:41 Arch-PC tracker-miner-f[2427]: Setting priority nice level to 19
mai 14 14:33:41 Arch-PC tracker-extract[2436]: Setting priority nice level to 19
mai 14 14:33:41 Arch-PC octopi-notifier[2451]: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
mai 14 14:33:42 Arch-PC octopi-notifier[2451]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
mai 14 14:33:42 Arch-PC octopi-notifier[2451]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
mai 14 14:33:42 Arch-PC audit[2451]: ANOM_ABEND auid=1004 uid=1004 gid=1004 ses=6 pid=2451 comm="octopi-notifier" exe="/usr/bin/octopi-notifier" sig=6 res=1
mai 14 14:33:45 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:33:45 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:33:45 Arch-PC kernel: kauditd_printk_skb: 16 callbacks suppressed
mai 14 14:33:45 Arch-PC kernel: audit: type=1131 audit(1589477625.725:158): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-2560-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:42 Arch-PC audit: AUDIT1334 prog-id=28 op=LOAD
mai 14 14:33:42 Arch-PC audit: AUDIT1334 prog-id=29 op=LOAD
mai 14 14:33:42 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-2560-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:42 Arch-PC audit[1934]: USER_END pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:33:42 Arch-PC audit[1934]: CRED_DISP pid=1934 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:33:42 Arch-PC audit[2622]: USER_AUTH pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:42 Arch-PC audit[2622]: USER_ACCT pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:42 Arch-PC audit[2622]: CRED_ACQ pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:43 Arch-PC audit[2622]: USER_START pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:33:45 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-2560-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:33:42 Arch-PC polkitd[535]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.124, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus)
mai 14 14:33:42 Arch-PC systemd[1]: Started Process Core Dump (PID 2560/UID 0).
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[1958]: dbus-daemon[1958]: [session uid=120 pid=1958] Activating service name='org.freedesktop.systemd1' requested by ':1.10' (uid=120 pid=2042 comm="/usr/lib/gsd-sharing ")
mai 14 14:33:45 Arch-PC gnome-shell[2597]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:45 Arch-PC gnome-shell[2597]: > Internal error: Could not resolve keysym XF86FullScreen
mai 14 14:33:45 Arch-PC gnome-shell[2597]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:43 Arch-PC gnome-session-binary[2630]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:42 Arch-PC systemd[2223]: Started GNOME Wacom handling.
mai 14 14:33:45 Arch-PC gnome-shell[2600]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:45 Arch-PC gnome-shell[2600]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:33:45 Arch-PC gnome-shell[2600]: > X11 cannot support keycodes above 255.
mai 14 14:33:45 Arch-PC gnome-shell[2600]: > Internal error: Could not resolve keysym Invalid
mai 14 14:33:45 Arch-PC gnome-shell[2600]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:43 Arch-PC gnome-session-binary[2630]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Wacom handling.
mai 14 14:33:44 Arch-PC polkitd[535]: Registered Authentication Agent for unix-session:c3 (system bus name :1.181 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 14 14:33:42 Arch-PC systemd[2223]: Started GNOME Color management.
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Successfully made thread 2695 of process 2695 owned by '120' high priority at nice level -11.
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Color management.
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:33:42 Arch-PC systemd[2223]: Started GNOME Keyboard handling.
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Supervising 4 threads of 2 processes of 2 users.
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Keyboard handling.
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2699]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Successfully made thread 2803 of process 2695 owned by '120' RT at priority 5.
mai 14 14:33:42 Arch-PC systemd[2223]: Started GNOME Power management handling.
mai 14 14:33:45 Arch-PC gnome-session[2630]: gnome-session-binary[2630]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC gnome-session[2630]: gnome-session-binary[2630]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Power management handling.
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=120 pid=2630 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=120 pid=2647 comm="/usr/bin/gnome-shell ")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Successfully activated service 'org.a11y.Bus'
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=120 pid=2647 comm="/usr/bin/gnome-shell ")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Successfully activated service 'ca.desrt.dconf'
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.2' (uid=120 pid=2647 comm="/usr/bin/gnome-shell ")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.gnome.Shell.Notifications' requested by ':1.2' (uid=120 pid=2647 comm="/usr/bin/gnome-shell ")
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Supervising 5 threads of 2 processes of 2 users.
mai 14 14:33:42 Arch-PC systemd[2223]: Started GNOME Media keys handling.
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2677]: dbus-daemon[2677]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=2647 comm="/usr/bin/gnome-shell ")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2677]: dbus-daemon[2677]: Successfully activated service 'org.a11y.atspi.Registry'
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Successfully made thread 2804 of process 2695 owned by '120' RT at priority 5.
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Media keys handling.
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2680]: glamor: No eglstream capable devices found
mai 14 14:33:45 Arch-PC pulseaudio[2695]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=120 pid=2700 comm="/usr/lib/gsd-sharing ")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Successfully activated service 'org.gnome.Shell.Notifications'
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=2647 comm="/usr/bin/gnome-shell ")
mai 14 14:33:45 Arch-PC /usr/lib/gdm-wayland-session[2629]: dbus-daemon[2629]: [session uid=120 pid=2629] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC rtkit-daemon[800]: Supervising 6 threads of 2 processes of 2 users.
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Session.
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2816]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2816]: > Internal error: Could not resolve keysym XF86FullScreen
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2816]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:45 Arch-PC dbus-daemon[494]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.190' (uid=120 pid=2695 comm="/usr/bin/pulseaudio --daemonize=no ")
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target GNOME Wayland Session (session: gnome).
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2822]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2822]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2822]: > X11 cannot support keycodes above 255.
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2822]: > Internal error: Could not resolve keysym Invalid
mai 14 14:33:45 Arch-PC org.gnome.Shell.desktop[2822]: Errors from xkbcomp are not fatal to the X server
mai 14 14:33:45 Arch-PC dbus-daemon[494]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
mai 14 14:33:42 Arch-PC systemd[2223]: Reached target Current graphical user session.
mai 14 14:33:42 Arch-PC unknown[1975]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:33:42 Arch-PC unknown[1975]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:33:42 Arch-PC gsd-media-keys[2407]: Failed to grab accelerator for keybinding settings:playback-repeat
mai 14 14:33:42 Arch-PC gsd-media-keys[2407]: Failed to grab accelerator for keybinding settings:playback-random
mai 14 14:33:42 Arch-PC gsd-media-keys[2407]: Failed to grab accelerator for keybinding settings:hibernate
mai 14 14:33:42 Arch-PC gsd-media-keys[2407]: Failed to grab accelerator for keybinding settings:rfkill
mai 14 14:33:42 Arch-PC gnome-shell[2289]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:42 Arch-PC systemd[2223]: GNOME session X11 services is not active.
mai 14 14:33:42 Arch-PC systemd[2223]: Dependency failed for GNOME XSettings.
mai 14 14:33:42 Arch-PC systemd[2223]: gsd-xsettings.target: Job gsd-xsettings.target/start failed with result 'dependency'.
mai 14 14:33:42 Arch-PC systemd[2223]: Starting GNOME XSettings...
mai 14 14:33:42 Arch-PC gnome-shell[2289]: GNOME Shell started at Thu May 14 2020 14:33:41 GMT-0300 (Horário Padrão de Brasília)
mai 14 14:33:42 Arch-PC gnome-shell[2289]: Registering session with GDM
mai 14 14:33:42 Arch-PC systemd[2223]: Started GNOME XSettings.
mai 14 14:33:42 Arch-PC systemd-logind[499]: Session c2 logged out. Waiting for processes to exit.
mai 14 14:33:42 Arch-PC systemd[1941]: pulseaudio.service: Succeeded.
mai 14 14:33:43 Arch-PC systemd[1]: session-c2.scope: Succeeded.
mai 14 14:33:43 Arch-PC systemd-logind[499]: Removed session c2.
mai 14 14:33:43 Arch-PC systemd-logind[499]: New session c3 of user gdm.
mai 14 14:33:43 Arch-PC systemd[1]: Started Session c3 of user gdm.
mai 14 14:33:44 Arch-PC gnome-shell[2647]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mai 14 14:33:44 Arch-PC gnome-shell[2647]: Will monitor session c3
mai 14 14:33:44 Arch-PC gnome-shell[2647]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:44 Arch-PC systemd[1941]: Starting Sound Service...
mai 14 14:33:44 Arch-PC gnome-shell[2647]: Failed to create file /run/user/120/gnome-shell-disable-extensions: Erro ao abrir arquivo “/run/user/120/gnome-shell-disable-extensions”: Arquivo existe
mai 14 14:33:44 Arch-PC gnome-shell[2647]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mai 14 14:33:45 Arch-PC gsd-sharing[2700]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC xbrlapi.desktop[2815]: openConnection: connect: Arquivo ou diretório inexistente
mai 14 14:33:45 Arch-PC xbrlapi.desktop[2815]: cannot connect to braille devices daemon brltty at :0
mai 14 14:33:45 Arch-PC gsd-sharing[2700]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC gsd-sharing[2700]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
mai 14 14:33:45 Arch-PC systemd[1941]: Started Sound Service.
mai 14 14:33:45 Arch-PC gnome-shell[2289]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:33:45 Arch-PC gnome-session-binary[2630]: Entering running state
mai 14 14:33:45 Arch-PC systemd-coredump[2561]: Process 2451 (octopi-notifier) of user 1004 dumped core.
Stack trace of thread 2451:
#0 0x00007f81401b02e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007f8140199853 abort (libc.so.6 + 0x25853)
#2 0x00007f81409279ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007f81411670e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007f8141167581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007f8140b502e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007f814116a5c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007f814186867a _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x16167a)
#8 0x0000560e8325989e main (octopi-notifier + 0x1489e)
#9 0x00007f814019b002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x0000560e832593be _start (octopi-notifier + 0x143be)
mai 14 14:33:45 Arch-PC systemd[1]: systemd-coredump@1-2560-0.service: Succeeded.
mai 14 14:33:46 Arch-PC kernel: audit: type=1334 audit(1589477626.035:159): prog-id=29 op=UNLOAD
mai 14 14:33:46 Arch-PC kernel: audit: type=1334 audit(1589477626.035:160): prog-id=28 op=UNLOAD
mai 14 14:33:46 Arch-PC audit: AUDIT1334 prog-id=29 op=UNLOAD
mai 14 14:33:46 Arch-PC audit: AUDIT1334 prog-id=28 op=UNLOAD
mai 14 14:33:45 Arch-PC gsd-media-keys[2718]: Failed to grab accelerator for keybinding settings:playback-repeat
mai 14 14:33:45 Arch-PC gsd-media-keys[2718]: Failed to grab accelerator for keybinding settings:hibernate
mai 14 14:33:45 Arch-PC gsd-media-keys[2718]: Failed to grab accelerator for keybinding settings:rfkill
mai 14 14:33:45 Arch-PC gsd-media-keys[2718]: Failed to grab accelerator for keybinding settings:playback-random
mai 14 14:33:45 Arch-PC gnome-shell[2647]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:33:45 Arch-PC gnome-shell[2647]: Registering session with GDM
mai 14 14:33:45 Arch-PC gnome-shell[2647]: Could not issue 'StartUnit' systemd call
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: xb_builder_node_unlink: assertion 'XB_IS_BUILDER_NODE (self)' failed
mai 14 14:33:46 Arch-PC gnome-software[2422]: plugin appstream took 3,9 seconds to do setup
mai 14 14:33:46 Arch-PC gnome-software[2422]: enabled plugins: desktop-categories, fwupd, os-release, provenance, appstream, provenance-license, desktop-menu-path, flatpak, generic-updates, hardcoded-blacklist, hardcoded-popular, modalias, rewrite-resource, icons, malcontent, odrs, key-colors, key-colors-metadata
mai 14 14:33:46 Arch-PC gnome-software[2422]: disabled plugins: dpkg, dummy, fedora-langpacks, fedora-pkgdb-collections, repos
mai 14 14:33:46 Arch-PC gnome-shell[2289]: WL: unknown object (11), message get_swipe_gesture(no)
mai 14 14:33:46 Arch-PC gnome-shell[2289]: WL: error in client communication (pid 2422)
mai 14 14:33:50 Arch-PC gnome-shell[2647]: Warning: Failed to start gsd-xsettings
mai 14 14:33:50 Arch-PC gnome-shell[2647]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
mai 14 14:33:51 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.54' (uid=1004 pid=2427 comm="/usr/lib/tracker-miner-fs ")
mai 14 14:33:51 Arch-PC systemd[2223]: Starting Tracker metadata extractor...
mai 14 14:33:51 Arch-PC tracker-extract[2849]: Set scheduler policy to SCHED_IDLE
mai 14 14:33:51 Arch-PC tracker-extract[2849]: Setting priority nice level to 19
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2863]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
mai 14 14:33:53 Arch-PC gst-plugin-scan[2648]: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
mai 14 14:33:54 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
mai 14 14:33:54 Arch-PC systemd[2223]: Started Tracker metadata extractor.
mai 14 14:33:54 Arch-PC tracker-extract[2436]: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Extract': D-Bus service name:'org.freedesktop.Tracker1.Miner.Extract' is already taken, perhaps the application is already running?
mai 14 14:33:54 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.62' (uid=1004 pid=2849 comm="/usr/lib/tracker-extract ")
mai 14 14:33:54 Arch-PC systemd[2223]: Starting Virtual filesystem metadata service...
mai 14 14:33:54 Arch-PC dbus-daemon[2241]: [session uid=1004 pid=2241] Successfully activated service 'org.gtk.vfs.Metadata'
mai 14 14:33:54 Arch-PC systemd[2223]: Started Virtual filesystem metadata service.
mai 14 14:33:54 Arch-PC tracker-extract[2849]: Unknown desktop entry type 'Application'
mai 14 14:34:04 Arch-PC systemd[2223]: tracker-extract.service: Succeeded.
mai 14 14:34:15 Arch-PC systemd[1]: systemd-localed.service: Succeeded.
mai 14 14:34:15 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:15 Arch-PC kernel: audit: type=1131 audit(1589477655.562:161): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:15 Arch-PC audit: AUDIT1334 prog-id=24 op=UNLOAD
mai 14 14:34:15 Arch-PC audit: AUDIT1334 prog-id=23 op=UNLOAD
mai 14 14:34:15 Arch-PC kernel: audit: type=1334 audit(1589477655.639:162): prog-id=24 op=UNLOAD
mai 14 14:34:15 Arch-PC kernel: audit: type=1334 audit(1589477655.639:163): prog-id=23 op=UNLOAD
mai 14 14:34:15 Arch-PC systemd[1]: systemd-hostnamed.service: Succeeded.
mai 14 14:34:15 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:15 Arch-PC kernel: audit: type=1131 audit(1589477655.722:164): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:15 Arch-PC audit: AUDIT1334 prog-id=26 op=UNLOAD
mai 14 14:34:15 Arch-PC audit: AUDIT1334 prog-id=25 op=UNLOAD
mai 14 14:34:15 Arch-PC kernel: audit: type=1334 audit(1589477655.789:165): prog-id=26 op=UNLOAD
mai 14 14:34:15 Arch-PC kernel: audit: type=1334 audit(1589477655.789:166): prog-id=25 op=UNLOAD
mai 14 14:34:17 Arch-PC geoclue[2025]: Service not used for 60 seconds. Shutting down..
mai 14 14:34:17 Arch-PC systemd[1]: geoclue.service: Succeeded.
mai 14 14:34:17 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:17 Arch-PC kernel: audit: type=1131 audit(1589477657.975:167): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:24 Arch-PC tracker-store[2532]: OK
mai 14 14:34:24 Arch-PC systemd[2223]: tracker-store.service: Succeeded.
mai 14 14:34:27 Arch-PC gdm-password][2902]: gkr-pam: unlocked login keyring
mai 14 14:34:27 Arch-PC audit[2902]: USER_AUTH pid=2902 uid=0 auid=1004 ses=5 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:27 Arch-PC kernel: audit: type=1100 audit(1589477667.399:168): pid=2902 uid=0 auid=1004 ses=5 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:27 Arch-PC audit[2902]: USER_ACCT pid=2902 uid=0 auid=1004 ses=5 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:27 Arch-PC kernel: audit: type=1101 audit(1589477667.432:169): pid=2902 uid=0 auid=1004 ses=5 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:27 Arch-PC audit[2902]: CRED_REFR pid=2902 uid=0 auid=1004 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:27 Arch-PC kernel: audit: type=1110 audit(1589477667.435:170): pid=2902 uid=0 auid=1004 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:27 Arch-PC gdm[517]: GLib: Source ID 110 was not found when attempting to remove it
mai 14 14:34:27 Arch-PC gnome-shell[2910]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:34:27 Arch-PC gnome-shell[2910]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:34:27 Arch-PC gnome-shell[2910]: > X11 cannot support keycodes above 255.
mai 14 14:34:27 Arch-PC gnome-shell[2910]: > Internal error: Could not resolve keysym Invalid
mai 14 14:34:27 Arch-PC gnome-shell[2910]: Errors from xkbcomp are not fatal to the X server
mai 14 14:34:33 Arch-PC gnome-shell[2289]: ../mutter/clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Date & Time handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Maintenance of expirable data.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME RFKill handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Smartcard handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME USB protection handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME WWan management.
mai 14 14:34:37 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping GNOME XSettings...
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-housekeeping.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Maintenance of expirable data.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Failed to launch ibus-daemon: Falha ao executar processo filho “ibus-daemon” (Arquivo ou diretório inexistente)
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Freedesktop screensaver handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-print-notifications.service: Killing process 2533 (gmain) with signal SIGKILL.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-screensaver-proxy.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Freedesktop screensaver handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Accessibility settings.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Printer notifications.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Sound sample caching handling.
mai 14 14:34:37 Arch-PC systemd[2223]: at-spi-dbus-bus.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-sharing.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-smartcard.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Smartcard handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Sharing handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-a11y-settings.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Accessibility settings.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-rfkill.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME RFKill handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-datetime.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Date & Time handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-sound.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Sound sample caching handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-usb-protection.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME USB protection handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-wwan.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME WWan management.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-print-notifications.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Printer notifications.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-xsettings.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME XSettings.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Wayland Session (session: gnome).
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target Current graphical user session.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Session.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Wayland Session.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Session (session: gnome).
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Color management.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Keyboard handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Media keys handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Power management handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Wacom handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping GNOME Color management...
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping GNOME Keyboard handling...
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping GNOME Media keys handling...
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping GNOME Power management handling...
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping GNOME Wacom handling...
mai 14 14:34:37 Arch-PC tracker-miner-fs.desktop[2427]: Received signal:15->'Terminado'
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x560f381fd460.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37ccf390.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37ccf390.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f3a2bd350.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f396118a0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f396118a0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f3a370840.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37c37870.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37c37870.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f396594c0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f3983c8d0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f3983c8d0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f38e42180.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f39b02c90.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f39b02c90.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f3adef870.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f38bc4de0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f38bc4de0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f3984b070.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f396037d0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f396037d0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f3a378650.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37c5c1e0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37c5c1e0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f399f3830.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37cda300.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f37cda300.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f38e54730.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f389135e0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f389135e0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: == Stack trace for context 0x560f376ed490 ==
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f38b43230.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f3984a690.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x560f3984a690.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x560f3983d870.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x560f3a37ac60.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was notify on NMDeviceEthernet 0x560f3a24c1f0.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was notify on NMActiveConnection 0x560f3a24e180.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was notify on NMActiveConnection 0x560f3a24e180.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mai 14 14:34:37 Arch-PC gnome-shell[2289]: The offending signal was state-changed on NMDeviceEthernet 0x560f3a24c1f0.
mai 14 14:34:37 Arch-PC tracker-miner-fs.desktop[2427]: OK
mai 14 14:34:37 Arch-PC systemd[2223]: gnome-session-manager@gnome.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Session Manager (session: gnome).
mai 14 14:34:37 Arch-PC gnome-shell[2317]: (EE) failed to read Wayland events: Broken pipe
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-wacom.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Wacom handling.
mai 14 14:34:37 Arch-PC systemd[2223]: gnome-shell-wayland.service: Killing process 2494 (Xwaylan:disk$0) with signal SIGKILL.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-keyboard.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Keyboard handling.
mai 14 14:34:37 Arch-PC polkitd[535]: Unregistered Authentication Agent for unix-session:5 (system bus name :1.153, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus)
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-power.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Power management handling.
mai 14 14:34:37 Arch-PC gsd-color[2708]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Electronics_23MP55_16843009_xanadu_1004
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-color.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Color management.
mai 14 14:34:37 Arch-PC systemd[2223]: gsd-media-keys.service: Succeeded.
mai 14 14:34:37 Arch-PC gnome-shell[2647]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permissão negada
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Media keys handling.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Session is initialized.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Shell on Wayland.
mai 14 14:34:37 Arch-PC systemd[2223]: gnome-shell-wayland.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped GNOME Shell on Wayland.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target GNOME Session Manager is ready.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target Tasks to be run before GNOME Session starts.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target Session services which should run early before the graphical session is brought up.
mai 14 14:34:37 Arch-PC systemd[2223]: Reached target Shutdown running GNOME Session.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping Monitor Session leader for GNOME Session...
mai 14 14:34:37 Arch-PC systemd[2223]: Starting Restart DBus after GNOME Session shutdown...
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target Shutdown running GNOME Session.
mai 14 14:34:37 Arch-PC systemd[2223]: Reached target Shutdown running GNOME Session.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped target Shutdown running GNOME Session.
mai 14 14:34:37 Arch-PC systemd[2223]: Started Restart DBus after GNOME Session shutdown.
mai 14 14:34:37 Arch-PC gdm-password][2215]: pam_unix(gdm-password:session): session closed for user xanadu
mai 14 14:34:37 Arch-PC systemd[2223]: gnome-session-monitor.service: Succeeded.
mai 14 14:34:37 Arch-PC audit[2215]: USER_END pid=2215 uid=0 auid=1004 ses=5 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:34:37 Arch-PC audit[2215]: USER_LOGOUT pid=2215 uid=0 auid=1004 ses=5 msg='uid=1004 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:34:37 Arch-PC audit[2215]: CRED_DISP pid=2215 uid=0 auid=1004 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped Monitor Session leader for GNOME Session.
mai 14 14:34:37 Arch-PC kernel: audit: type=1106 audit(1589477677.722:171): pid=2215 uid=0 auid=1004 ses=5 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:34:37 Arch-PC kernel: audit: type=1113 audit(1589477677.722:172): pid=2215 uid=0 auid=1004 ses=5 msg='uid=1004 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:34:37 Arch-PC kernel: audit: type=1104 audit(1589477677.722:173): pid=2215 uid=0 auid=1004 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:34:37 Arch-PC kernel: rfkill: input handler disabled
mai 14 14:34:37 Arch-PC systemd[1941]: run-user-1004-gvfs.mount: Succeeded.
mai 14 14:34:37 Arch-PC gvfsd[2346]: A connection to the bus can't be made
mai 14 14:34:37 Arch-PC systemd[2223]: Stopping D-Bus User Message Bus...
mai 14 14:34:37 Arch-PC systemd[2223]: run-user-1004-gvfs.mount: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
mai 14 14:34:37 Arch-PC systemd[2223]: xdg-permission-store.service: Failed with result 'exit-code'.
mai 14 14:34:37 Arch-PC systemd[2223]: gvfs-udisks2-volume-monitor.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[1]: run-user-1004-gvfs.mount: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: gnome-session-restart-dbus.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: evolution-source-registry.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: evolution-addressbook-factory.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: gvfs-daemon.service: Succeeded.
mai 14 14:34:37 Arch-PC pulseaudio[2271]: E: [pulseaudio] stdin-util.c: Unable to read or parse data from client.
mai 14 14:34:37 Arch-PC systemd[2223]: dbus.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Stopped D-Bus User Message Bus.
mai 14 14:34:37 Arch-PC systemd[2223]: evolution-calendar-factory.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: Started D-Bus User Message Bus.
mai 14 14:34:37 Arch-PC systemd[2223]: pulseaudio.service: Succeeded.
mai 14 14:34:37 Arch-PC systemd[2223]: gvfs-metadata.service: Succeeded.
mai 14 14:34:38 Arch-PC systemd[1]: session-5.scope: Succeeded.
mai 14 14:34:38 Arch-PC systemd-logind[499]: Session 5 logged out. Waiting for processes to exit.
mai 14 14:34:38 Arch-PC systemd-logind[499]: Removed session 5.
mai 14 14:34:38 Arch-PC org.gnome.Shell.desktop[2946]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:34:38 Arch-PC org.gnome.Shell.desktop[2946]: > Warning: Unsupported maximum keycode 569, clipping.
mai 14 14:34:38 Arch-PC org.gnome.Shell.desktop[2946]: > X11 cannot support keycodes above 255.
mai 14 14:34:38 Arch-PC org.gnome.Shell.desktop[2946]: > Internal error: Could not resolve keysym Invalid
mai 14 14:34:38 Arch-PC org.gnome.Shell.desktop[2946]: Errors from xkbcomp are not fatal to the X server
mai 14 14:34:48 Arch-PC systemd[1]: Stopping User Manager for UID 1004...
mai 14 14:34:48 Arch-PC systemd[2223]: Removed slice gnome\x2dsession\x2dmanager.slice.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopped target Main User Target.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopping D-Bus User Message Bus...
mai 14 14:34:48 Arch-PC systemd[2223]: dbus.service: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopped D-Bus User Message Bus.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopped target Basic System.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopped target Paths.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopped target Sockets.
mai 14 14:34:48 Arch-PC systemd[2223]: Stopped target Timers.
mai 14 14:34:48 Arch-PC systemd[2223]: dbus.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed D-Bus User Message Bus Socket.
mai 14 14:34:48 Arch-PC systemd[2223]: dirmngr.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed GnuPG network certificate management daemon.
mai 14 14:34:48 Arch-PC systemd[2223]: gpg-agent-browser.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:34:48 Arch-PC systemd[2223]: gpg-agent-extra.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:34:48 Arch-PC systemd[2223]: gpg-agent-ssh.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:34:48 Arch-PC systemd[2223]: gpg-agent.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed GnuPG cryptographic agent and passphrase cache.
mai 14 14:34:48 Arch-PC systemd[2223]: p11-kit-server.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed p11-kit server.
mai 14 14:34:48 Arch-PC systemd[2223]: pipewire.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed Multimedia System.
mai 14 14:34:48 Arch-PC systemd[2223]: pulseaudio.socket: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Closed Sound System.
mai 14 14:34:48 Arch-PC systemd[2223]: Reached target Shutdown.
mai 14 14:34:48 Arch-PC systemd[2223]: systemd-exit.service: Succeeded.
mai 14 14:34:48 Arch-PC systemd[2223]: Finished Exit the Session.
mai 14 14:34:48 Arch-PC systemd[2223]: Reached target Exit the Session.
mai 14 14:34:48 Arch-PC systemd[2224]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[xanadu] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:34:48 Arch-PC systemd[1]: user@1004.service: Succeeded.
mai 14 14:34:48 Arch-PC systemd[1]: Stopped User Manager for UID 1004.
mai 14 14:34:48 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:48 Arch-PC kernel: audit: type=1131 audit(1589477688.442:174): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:48 Arch-PC systemd[1]: Stopping User Runtime Directory /run/user/1004...
mai 14 14:34:48 Arch-PC systemd[1]: run-user-1004.mount: Succeeded.
mai 14 14:34:48 Arch-PC systemd[1941]: run-user-1004.mount: Succeeded.
mai 14 14:34:48 Arch-PC systemd[1]: user-runtime-dir@1004.service: Succeeded.
mai 14 14:34:48 Arch-PC systemd[1]: Stopped User Runtime Directory /run/user/1004.
mai 14 14:34:48 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:48 Arch-PC systemd[1]: Removed slice User Slice of UID 1004.
mai 14 14:34:48 Arch-PC kernel: audit: type=1131 audit(1589477688.459:175): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC gdm-password][2949]: gkr-pam: unable to locate daemon control file
mai 14 14:34:49 Arch-PC audit[2949]: USER_AUTH pid=2949 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:49 Arch-PC gdm-password][2949]: gkr-pam: stashed password to try later in open session
mai 14 14:34:49 Arch-PC kernel: audit: type=1100 audit(1589477689.245:176): pid=2949 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:49 Arch-PC audit[2949]: USER_ACCT pid=2949 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:49 Arch-PC kernel: audit: type=1101 audit(1589477689.265:177): pid=2949 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:49 Arch-PC audit[2949]: CRED_ACQ pid=2949 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:49 Arch-PC kernel: audit: type=1103 audit(1589477689.269:178): pid=2949 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:34:49 Arch-PC gdm-password][2949]: pam_unix(gdm-password:session): session opened for user xanadu by (uid=0)
mai 14 14:34:49 Arch-PC kernel: audit: type=1006 audit(1589477689.312:179): pid=2949 uid=0 old-auid=4294967295 auid=1004 tty=(none) old-ses=4294967295 ses=7 res=1
mai 14 14:34:49 Arch-PC systemd[1]: Created slice User Slice of UID 1004.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/1004...
mai 14 14:34:49 Arch-PC systemd-logind[499]: New session 7 of user xanadu.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in First Boot Wizard being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Create System Users being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Condition check resulted in Update is Completed being skipped.
mai 14 14:34:49 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/1004.
mai 14 14:34:49 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC systemd[1]: Starting User Manager for UID 1004...
mai 14 14:34:49 Arch-PC kernel: audit: type=1130 audit(1589477689.352:180): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC audit[2954]: USER_ACCT pid=2954 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC audit[2954]: CRED_ACQ pid=2954 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:34:49 Arch-PC systemd[2954]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[xanadu] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:34:49 Arch-PC systemd[2954]: pam_unix(systemd-user:session): session opened for user xanadu by (uid=0)
mai 14 14:34:49 Arch-PC audit[2954]: USER_START pid=2954 uid=0 auid=1004 ses=8 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC kernel: audit: type=1101 audit(1589477689.362:181): pid=2954 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC kernel: audit: type=1103 audit(1589477689.362:182): pid=2954 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="xanadu" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:34:49 Arch-PC kernel: audit: type=1006 audit(1589477689.362:183): pid=2954 uid=0 old-auid=4294967295 auid=1004 tty=(none) old-ses=4294967295 ses=8 res=1
mai 14 14:34:49 Arch-PC audit: AUDIT1334 prog-id=30 op=LOAD
mai 14 14:34:49 Arch-PC audit: AUDIT1334 prog-id=30 op=UNLOAD
mai 14 14:34:49 Arch-PC systemd[2954]: Reached target Paths.
mai 14 14:34:49 Arch-PC systemd[2954]: Reached target Timers.
mai 14 14:34:49 Arch-PC systemd[2954]: Starting D-Bus User Message Bus Socket.
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on GnuPG network certificate management daemon.
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on p11-kit server.
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on Multimedia System.
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on Sound System.
mai 14 14:34:49 Arch-PC systemd[2954]: Listening on D-Bus User Message Bus Socket.
mai 14 14:34:49 Arch-PC systemd[2954]: Reached target Sockets.
mai 14 14:34:49 Arch-PC systemd[2954]: Reached target Basic System.
mai 14 14:34:49 Arch-PC systemd[1]: Started User Manager for UID 1004.
mai 14 14:34:49 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1004 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC systemd[1]: Started Session 7 of user xanadu.
mai 14 14:34:49 Arch-PC systemd[2954]: Starting Update XDG user dir configuration...
mai 14 14:34:49 Arch-PC systemd[2954]: xdg-user-dirs-update.service: Succeeded.
mai 14 14:34:49 Arch-PC systemd[2954]: Finished Update XDG user dir configuration.
mai 14 14:34:49 Arch-PC systemd[2954]: Reached target Main User Target.
mai 14 14:34:49 Arch-PC systemd[2954]: Startup finished in 107ms.
mai 14 14:34:49 Arch-PC gdm-password][2949]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
mai 14 14:34:49 Arch-PC audit[2949]: USER_START pid=2949 uid=0 auid=1004 ses=7 msg='op=PAM:session_open grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="xanadu" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty2 res=success'
mai 14 14:34:49 Arch-PC audit[2949]: USER_LOGIN pid=2949 uid=0 auid=1004 ses=7 msg='uid=1004 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
mai 14 14:34:49 Arch-PC kernel: rfkill: input handler enabled
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (--) Log file renamed from "/home/xanadu/.local/share/xorg/Xorg.pid-2972.log" to "/home/xanadu/.local/share/xorg/Xorg.0.log"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) Failed to open protocol names file lib/xorg/protocol.txt
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: X.Org X Server 1.20.8
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: X Protocol Version 11, Revision 0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Build Operating System: Linux Arch Linux
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Current Operating System: Linux Arch-PC 5.6.12-arch1-1 #1 SMP PREEMPT Sun, 10 May 2020 10:43:42 +0000 x86_64
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81 rw scsi_mod.use_blk_mq=1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Build Date: 05 May 2020 05:08:17AM
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]:
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Current version of pixman: 0.40.0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Before reporting problems, check http://wiki.x.org
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: to make sure that you have the latest version.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Markers: (--) probed, (**) from config file, (==) default setting,
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (++) from command line, (!!) notice, (II) informational,
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Log file: "/home/xanadu/.local/share/xorg/Xorg.0.log", Time: Thu May 14 14:34:49 2020
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) No Layout section. Using the first Screen section.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) No screen section available. Using defaults.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (**) |-->Screen "Default Screen Section" (0)
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (**) | |-->Monitor "<default monitor>"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) No monitor specified for screen "Default Screen Section".
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Using a default monitor configuration.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Automatically adding devices
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Automatically enabling devices
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Automatically adding GPU devices
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Automatically binding GPU devices
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Max clients allowed: 256, resource mask: 0x1fffff
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) The directory "/usr/share/fonts/Type1" does not exist.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Entry deleted from font path.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) FontPath set to:
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: /usr/share/fonts/misc,
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: /usr/share/fonts/TTF,
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: /usr/share/fonts/OTF,
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: /usr/share/fonts/100dpi,
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: /usr/share/fonts/75dpi
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) ModulePath set to "/usr/lib/xorg/modules"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) The server relies on udev to provide the list of input devices.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: If no devices become available, reconfigure udev or disable AutoAddDevices.
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module ABI versions:
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: X.Org ANSI C Emulation: 0.4
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: X.Org Video Driver: 24.1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: X.Org XInput driver : 24.1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: X.Org Server Extension : 10.0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (++) using VT number 2
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: took control of session /org/freedesktop/login1/session/_37
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) xfree86: Adding drm device (/dev/dri/card0)
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (--) PCI:*(0@0:2:0) 8086:0402:1458:d000 rev 6, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "glx"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module glx: vendor="X.Org Foundation"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: compiled for 1.20.8, module version = 1.0.0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: ABI class: X.Org Server Extension, version 10.0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Matched intel as autoconfigured driver 0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Matched modesetting as autoconfigured driver 1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Matched fbdev as autoconfigured driver 2
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Matched vesa as autoconfigured driver 3
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) Assigned the driver to the xf86ConfigLayout
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "intel"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) Warning, couldn't open module intel
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (EE) Failed to load module "intel" (module does not exist, 0)
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "modesetting"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module modesetting: vendor="X.Org Foundation"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: compiled for 1.20.8, module version = 1.20.8
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Module class: X.Org Video Driver
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: ABI class: X.Org Video Driver, version 24.1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "fbdev"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) Warning, couldn't open module fbdev
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (EE) Failed to load module "fbdev" (module does not exist, 0)
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "vesa"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module vesa: vendor="X.Org Foundation"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: compiled for 1.20.8, module version = 2.4.0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: Module class: X.Org Video Driver
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: ABI class: X.Org Video Driver, version 24.1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) VESA: driver for VESA chipsets: vesa
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): using drv /dev/dri/card0
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Creating default Display subsection in Screen section
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: "Default Screen Section" for depth/fbbpp 24/32
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): Depth 24, (==) framebuffer bpp 32
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): RGB weight 888
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): Default visual is TrueColor
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading sub module "glamoregl"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "glamoregl"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module glamoregl: vendor="X.Org Foundation"
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: compiled for 1.20.8, module version = 1.0.1
mai 14 14:34:49 Arch-PC /usr/lib/gdm-x-session[2972]: ABI class: X.Org ANSI C Emulation, version 0.4
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) HD Graphics (HSW GT1)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): glamor initialized
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output VGA-1 has no monitor section
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-1 has no monitor section
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-2 has no monitor section
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output DP-1 has no monitor section
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-3 has no monitor section
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID for output VGA-1
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID for output HDMI-1
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Manufacturer: GSM Model: 5a23 Serial#: 16843009
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Year: 2017 Week: 10
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID Version: 1.3
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Digital Display Input
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Max Image Size [cm]: horiz.: 51 vert.: 29
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Gamma: 2.20
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): DPMS capabilities: StandBy Suspend Off
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): First detailed timing is preferred mode
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): redX: 0.638 redY: 0.334 greenX: 0.309 greenY: 0.627
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): blueX: 0.153 blueY: 0.073 whiteX: 0.313 whiteY: 0.329
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported established timings:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 640x480@60Hz
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 800x600@60Hz
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 1024x768@60Hz
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Manufacturer's mask: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported standard timings:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 60 vid: 16497
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #1: hsize: 1280 vsize 720 refresh: 60 vid: 49281
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #2: hsize: 1280 vsize 800 refresh: 60 vid: 129
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #5: hsize: 1400 vsize 1050 refresh: 60 vid: 16528
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #6: hsize: 1600 vsize 900 refresh: 60 vid: 49321
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): #7: hsize: 1680 vsize 1050 refresh: 60 vid: 179
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported detailed timing:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): clock: 148.5 MHz Image Size: 510 x 290 mm
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Ranges: V min: 56 V max: 61 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Monitor name: 23MP55
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Serial No:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported detailed timing:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): clock: 148.5 MHz Image Size: 510 x 290 mm
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported detailed timing:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): clock: 74.2 MHz Image Size: 510 x 290 mm
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported detailed timing:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): clock: 74.2 MHz Image Size: 510 x 290 mm
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Supported detailed timing:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): clock: 27.0 MHz Image Size: 510 x 290 mm
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Number of EDID sections to follow: 1
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID (in hex):
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 00ffffffffffff001e6d235a01010101
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 0a1b010380331d78ea6275a3554fa027
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 125054210800714081c0810081809500
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 9040a9c0b300023a801871382d40582c
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 4500fe221100001e000000fd00383d1e
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 530f000a202020202020000000fc0032
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 334d5035350a202020202020000000ff
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 000a202020202020202020202020016c
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 02031df14a900403011412051f101323
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 0907078301000065030c001000023a80
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 1871382d40582c4500fe221100001e01
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 1d8018711c1620582c2500fe22110000
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 9e011d007251d01e206e285500fe2211
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 00001e8c0ad08a20e02d10103e9600fe
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 22110000180000000000000000000000
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): 000000000000000000000000000000e6
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Printing probed modes for output HDMI-1
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1920x1080i"x59.9 74.18 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1400x1050"x59.9 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1600x900"x60.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID for output HDMI-2
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID for output DP-1
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): EDID for output HDMI-3
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output VGA-1 disconnected
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-1 connected
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-2 disconnected
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output DP-1 disconnected
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-3 disconnected
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Using exact sizes for initial modes
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Output HDMI-1 using initial mode 1920x1080 +0+0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): DPI set to (96, 96)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading sub module "fb"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "fb"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading /usr/lib/xorg/modules/libfb.so
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module fb: vendor="X.Org Foundation"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: compiled for 1.20.8, module version = 1.0.0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: ABI class: X.Org ANSI C Emulation, version 0.4
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) UnloadModule: "vesa"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Unloading vesa
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): Backing store enabled
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): Silken mouse disabled
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (==) modeset(0): DPMS enabled
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): [DRI2] Setup complete
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): [DRI2] DRI driver: i965
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): [DRI2] VDPAU driver: va_gl
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension Generic Event Extension
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension SHAPE
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension MIT-SHM
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XInputExtension
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XTEST
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension BIG-REQUESTS
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension SYNC
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XKEYBOARD
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XC-MISC
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension SECURITY
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XFIXES
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension RENDER
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension RANDR
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension COMPOSITE
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension DAMAGE
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension MIT-SCREEN-SAVER
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension DOUBLE-BUFFER
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension RECORD
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension DPMS
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension Present
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension DRI3
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension X-Resource
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XVideo
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XVideo-MotionCompensation
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension GLX
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) AIGLX: Loaded and initialized i965
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) GLX: Initialized DRI2 GL provider for screen 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XFree86-VidModeExtension
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XFree86-DGA
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension XFree86-DRI
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Initializing extension DRI2
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Damage tracking initialized
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) modeset(0): Setting screen physical size to 508 x 285
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2981]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2981]: > Internal error: Could not resolve keysym XF86FullScreen
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2981]: Errors from xkbcomp are not fatal to the X server
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Power Button (/dev/input/event1)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Power Button: Applying InputClass "libinput keyboard catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) LoadModule: "libinput"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Module libinput: vendor="X.Org Foundation"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: compiled for 1.20.7, module version = 0.29.0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: Module class: X.Org XInput Driver
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: ABI class: X.Org XInput driver, version 24.1
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Power Button'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 16 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Power Button: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event1"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event1 - Power Button: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event1 - Power Button: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event1 - Power Button: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event1 - Power Button: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event1 - Power Button: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Video Bus (/dev/input/event7)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Video Bus: Applying InputClass "libinput keyboard catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Video Bus'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 19 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Video Bus: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event7"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event7 - Video Bus: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event7 - Video Bus: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event7 - Video Bus: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7/event7"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event7 - Video Bus: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event7 - Video Bus: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Power Button (/dev/input/event0)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Power Button: Applying InputClass "libinput keyboard catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Power Button'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 20 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Power Button: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event0"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event0 - Power Button: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event0 - Power Button: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event0 - Power Button: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event0 - Power Button: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event0 - Power Button: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event13)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event14)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event15)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=9 (/dev/input/event16)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=10 (/dev/input/event17)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event5)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Optical Mouse: Applying InputClass "libinput pointer catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Logitech USB Optical Mouse'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 21 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Optical Mouse: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event5"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event5 - Logitech USB Optical Mouse: is tagged by udev as: Mouse
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event5 - Logitech USB Optical Mouse: device is a pointer
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event5 - Logitech USB Optical Mouse: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/0003:046D:C077.0003/input/input5/event5"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 9)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "AccelerationScheme" "none"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Optical Mouse: (accel) selected scheme none/0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event5 - Logitech USB Optical Mouse: is tagged by udev as: Mouse
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event5 - Logitech USB Optical Mouse: device is a pointer
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event2)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Keyboard: Applying InputClass "libinput keyboard catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Logitech USB Keyboard'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 22 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Keyboard: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event2"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event2 - Logitech USB Keyboard: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event2 - Logitech USB Keyboard: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event2 - Logitech USB Keyboard: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/0003:046D:C31C.0001/input/input2/event2"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 10)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event2 - Logitech USB Keyboard: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event2 - Logitech USB Keyboard: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Logitech USB Keyboard Consumer Control (/dev/input/event3)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Keyboard Consumer Control: Applying InputClass "libinput keyboard catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Logitech USB Keyboard Consumer Control'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 23 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Keyboard Consumer Control: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event3"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event3 - Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event3 - Logitech USB Keyboard Consumer Control: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event3 - Logitech USB Keyboard Consumer Control: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/input/input3/event3"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Logitech USB Keyboard Consumer Control" (type: KEYBOARD, id 11)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event3 - Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event3 - Logitech USB Keyboard Consumer Control: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device Logitech USB Keyboard System Control (/dev/input/event4)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Keyboard System Control: Applying InputClass "libinput keyboard catchall"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) Using input driver 'libinput' for 'Logitech USB Keyboard System Control'
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 24 paused 0
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Logitech USB Keyboard System Control: always reports core events
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "Device" "/dev/input/event4"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "_source" "server/udev"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event4 - Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event4 - Logitech USB Keyboard System Control: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event4 - Logitech USB Keyboard System Control: device removed
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.1/0003:046D:C31C.0002/input/input4/event4"
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) XINPUT: Adding extended input device "Logitech USB Keyboard System Control" (type: KEYBOARD, id 12)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event4 - Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event4 - Logitech USB Keyboard System Control: device is a keyboard
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event10)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event11)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event9)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) No input driver specified, ignoring this device.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2972]: (II) This device may have been added with another device file.
mai 14 14:34:50 Arch-PC systemd[2954]: Started D-Bus User Message Bus.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2984]: /etc/gdm/Xsession: Beginning session setup...
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2994]: localuser:xanadu being added to access control list
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2984]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/startplasma-x11
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2997]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2997]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
mai 14 14:34:50 Arch-PC /usr/lib/gdm-x-session[2997]: Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
mai 14 14:34:50 Arch-PC audit[2997]: ANOM_ABEND auid=1004 uid=1004 gid=1004 ses=7 pid=2997 comm="kapplymousethem" exe="/usr/bin/kapplymousetheme" sig=6 res=1
mai 14 14:34:50 Arch-PC audit: AUDIT1334 prog-id=31 op=LOAD
mai 14 14:34:50 Arch-PC audit: AUDIT1334 prog-id=32 op=LOAD
mai 14 14:34:50 Arch-PC systemd[1]: Started Process Core Dump (PID 2998/UID 0).
mai 14 14:34:50 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@2-2998-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:51 Arch-PC /usr/lib/gdm-x-session[2984]: "kapplymousetheme" ("breeze_cursors", "24") exited with code 6
mai 14 14:34:51 Arch-PC dbus-daemon[2982]: [session uid=1004 pid=2982] Activating service name='org.kde.KSplash' requested by ':1.4' (uid=1004 pid=2984 comm="/usr/bin/startplasma-x11 ")
mai 14 14:34:51 Arch-PC systemd-coredump[2999]: Process 2997 (kapplymousethem) of user 1004 dumped core.
Stack trace of thread 2997:
#0 0x00007f32de2662e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007f32de24f853 abort (libc.so.6 + 0x25853)
#2 0x00007f32de6609ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007f32dec540e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007f32dec54581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007f32de8892e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007f32dec575c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007f32dec58528 _ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x137528)
#8 0x000055a01543b06e n/a (kapplymousetheme + 0x506e)
#9 0x00007f32de251002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x000055a01543b28e _start (kapplymousetheme + 0x528e)
mai 14 14:34:51 Arch-PC systemd[1]: systemd-coredump@2-2998-0.service: Succeeded.
mai 14 14:34:51 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@2-2998-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:51 Arch-PC audit: AUDIT1334 prog-id=32 op=UNLOAD
mai 14 14:34:51 Arch-PC audit: AUDIT1334 prog-id=31 op=UNLOAD
mai 14 14:34:52 Arch-PC /usr/lib/gdm-x-session[3018]: kdeinit5: preparing to launch '/usr/lib/kf5/klauncher'
mai 14 14:34:52 Arch-PC /usr/lib/gdm-x-session[3018]: kdeinit5: Launched KLauncher, pid = 3019, result = 0
mai 14 14:34:52 Arch-PC klauncher[3019]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
mai 14 14:34:52 Arch-PC audit[3019]: ANOM_ABEND auid=1004 uid=1004 gid=1004 ses=7 pid=3019 comm="klauncher" exe="/usr/lib/kf5/klauncher" sig=6 res=1
mai 14 14:34:52 Arch-PC klauncher[3019]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
mai 14 14:34:52 Arch-PC audit: AUDIT1334 prog-id=33 op=LOAD
mai 14 14:34:52 Arch-PC audit: AUDIT1334 prog-id=34 op=LOAD
mai 14 14:34:52 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@3-3020-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:52 Arch-PC systemd[1]: Started Process Core Dump (PID 3020/UID 0).
mai 14 14:34:53 Arch-PC /usr/lib/gdm-x-session[3018]: kdeinit5: Communication error with launcher. Exiting!
mai 14 14:34:53 Arch-PC systemd-coredump[3023]: Process 3019 (klauncher) of user 1004 dumped core.
Stack trace of thread 3019:
#0 0x00007fb9f9fb32e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007fb9f9f9c853 abort (libc.so.6 + 0x25853)
#2 0x00007fb9f8d8f9ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007fb9f94b50e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007fb9f94b5581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007fb9f8fb82e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007fb9f94b85c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007fb9f94b9528 _ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x137528)
#8 0x00007fb9fa14eb9c kdemain (libkdeinit5_klauncher.so + 0x10b9c)
#9 0x00007fb9f9f9e002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x0000559be6b1f05e n/a (klauncher + 0x105e)
mai 14 14:34:53 Arch-PC systemd[1]: systemd-coredump@3-3020-0.service: Succeeded.
mai 14 14:34:53 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@3-3020-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:53 Arch-PC audit[3030]: ANOM_ABEND auid=1004 uid=1004 gid=1004 ses=7 pid=3030 comm="kcminit_startup" exe="/usr/bin/kcminit_startup" sig=6 res=1
mai 14 14:34:53 Arch-PC audit: AUDIT1334 prog-id=35 op=LOAD
mai 14 14:34:53 Arch-PC audit: AUDIT1334 prog-id=36 op=LOAD
mai 14 14:34:53 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@4-3031-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:53 Arch-PC audit: AUDIT1334 prog-id=34 op=UNLOAD
mai 14 14:34:53 Arch-PC audit: AUDIT1334 prog-id=33 op=UNLOAD
mai 14 14:34:53 Arch-PC systemd[1]: Started Process Core Dump (PID 3031/UID 0).
mai 14 14:34:53 Arch-PC /usr/lib/gdm-x-session[3007]: org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0
mai 14 14:34:53 Arch-PC kded5[3034]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
mai 14 14:34:53 Arch-PC audit[3034]: ANOM_ABEND auid=1004 uid=1004 gid=1004 ses=7 pid=3034 comm="kded5" exe="/usr/bin/kded5" sig=6 res=1
mai 14 14:34:53 Arch-PC kded5[3034]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
mai 14 14:34:53 Arch-PC kernel: kauditd_printk_skb: 24 callbacks suppressed
mai 14 14:34:54 Arch-PC kernel: audit: type=1701 audit(1589477693.785:208): auid=1004 uid=1004 gid=1004 ses=7 pid=3034 comm="kded5" exe="/usr/bin/kded5" sig=6 res=1
mai 14 14:34:54 Arch-PC kernel: audit: type=1334 audit(1589477693.795:209): prog-id=37 op=LOAD
mai 14 14:34:54 Arch-PC kernel: audit: type=1334 audit(1589477693.795:210): prog-id=38 op=LOAD
mai 14 14:34:54 Arch-PC kernel: audit: type=1130 audit(1589477693.795:211): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-3035-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:54 Arch-PC kernel: audit: type=1131 audit(1589477693.935:212): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@4-3031-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:53 Arch-PC audit: AUDIT1334 prog-id=37 op=LOAD
mai 14 14:34:53 Arch-PC audit: AUDIT1334 prog-id=38 op=LOAD
mai 14 14:34:53 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-3035-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:53 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@4-3031-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:53 Arch-PC systemd[1]: Started Process Core Dump (PID 3035/UID 0).
mai 14 14:34:53 Arch-PC systemd-coredump[3032]: Process 3030 (kcminit_startup) of user 1004 dumped core.
Stack trace of thread 3030:
#0 0x00007fb1e9b762e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007fb1e9b5f853 abort (libc.so.6 + 0x25853)
#2 0x00007fb1e8d2c9ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007fb1e93200e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007fb1e9320581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007fb1e8f552e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007fb1e93235c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007fb1e9324528 _ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x137528)
#8 0x00007fb1e9d06828 kdemain (libkdeinit5_kcminit_startup.so + 0x5828)
#9 0x00007fb1e9b61002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x0000556bce2de05e _start (kcminit_startup + 0x105e)
mai 14 14:34:53 Arch-PC systemd[1]: systemd-coredump@4-3031-0.service: Succeeded.
mai 14 14:34:54 Arch-PC audit: AUDIT1334 prog-id=36 op=UNLOAD
mai 14 14:34:54 Arch-PC audit: AUDIT1334 prog-id=35 op=UNLOAD
mai 14 14:34:54 Arch-PC kernel: audit: type=1334 audit(1589477694.089:213): prog-id=36 op=UNLOAD
mai 14 14:34:54 Arch-PC kernel: audit: type=1334 audit(1589477694.089:214): prog-id=35 op=UNLOAD
mai 14 14:34:54 Arch-PC systemd-coredump[3038]: Process 3034 (kded5) of user 1004 dumped core.
Stack trace of thread 3034:
#0 0x00007f0e3fb2d2e5 raise (libc.so.6 + 0x3c2e5)
#1 0x00007f0e3fb16853 abort (libc.so.6 + 0x25853)
#2 0x00007f0e3ff259ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x00007f0e406bb0e6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1330e6)
#4 0x00007f0e406bb581 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x133581)
#5 0x00007f0e4014e2e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x00007f0e406be5c0 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x00007f0e40e9267a _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x16167a)
#8 0x0000565549f8f9ed n/a (kded5 + 0x69ed)
#9 0x00007f0e3fb18002 __libc_start_main (libc.so.6 + 0x27002)
#10 0x0000565549f8fa5e n/a (kded5 + 0x6a5e)
mai 14 14:34:54 Arch-PC kernel: audit: type=1131 audit(1589477694.345:215): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-3035-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:54 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-3035-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:34:54 Arch-PC systemd[1]: systemd-coredump@5-3035-0.service: Succeeded.
mai 14 14:34:54 Arch-PC audit: AUDIT1334 prog-id=38 op=UNLOAD
mai 14 14:34:54 Arch-PC audit: AUDIT1334 prog-id=37 op=UNLOAD
mai 14 14:34:54 Arch-PC kernel: audit: type=1334 audit(1589477694.615:216): prog-id=38 op=UNLOAD
mai 14 14:34:54 Arch-PC kernel: audit: type=1334 audit(1589477694.615:217): prog-id=37 op=UNLOAD
mai 14 14:35:00 Arch-PC gnome-session[2630]: gnome-session-binary[2630]: WARNING: Lost name on bus: org.gnome.SessionManager
mai 14 14:35:00 Arch-PC gnome-session-binary[2630]: WARNING: Lost name on bus: org.gnome.SessionManager
mai 14 14:35:00 Arch-PC gsd-rfkill[2712]: Error releasing name org.gnome.SettingsDaemon.Rfkill: A conexão está fechada
mai 14 14:35:00 Arch-PC gsd-print-notif[2711]: Error releasing name org.gnome.SettingsDaemon.PrintNotifications: A conexão está fechada
mai 14 14:35:00 Arch-PC audit[2622]: USER_END pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:35:00 Arch-PC audit[2622]: CRED_DISP pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:35:00 Arch-PC kernel: audit: type=1106 audit(1589477700.679:218): pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_succeed_if,pam_systemd,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:35:00 Arch-PC kernel: audit: type=1104 audit(1589477700.679:219): pid=2622 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=Arch-PC addr=? terminal=/dev/tty1 res=success'
mai 14 14:35:00 Arch-PC systemd-logind[499]: Session c3 logged out. Waiting for processes to exit.
mai 14 14:35:00 Arch-PC polkitd[535]: Unregistered Authentication Agent for unix-session:c3 (system bus name :1.181, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus)
mai 14 14:35:00 Arch-PC systemd[1]: session-c3.scope: Succeeded.
mai 14 14:35:00 Arch-PC systemd-logind[499]: Removed session c3.
mai 14 14:35:00 Arch-PC systemd[1941]: pulseaudio.service: Succeeded.
mai 14 14:35:00 Arch-PC gdm[517]: Child process -2625 was already dead.
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "16"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event1 - Power Button: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "19"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event7 - Video Bus: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "20"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event0 - Power Button: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "21"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event5 - Logitech USB Optical Mouse: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "22"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event2 - Logitech USB Keyboard: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "23"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event3 - Logitech USB Keyboard Consumer Control: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (**) Option "fd" "24"
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) event4 - Logitech USB Keyboard System Control: device removed
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) AIGLX: Suspending AIGLX clients for VT switch
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:66
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 226:0
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:64
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:71
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:65
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:68
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:67
mai 14 14:35:04 Arch-PC /usr/lib/gdm-x-session[2972]: (II) systemd-logind: got pause for 13:69
mai 14 14:35:04 Arch-PC systemd[1]: Started Getty on tty3.
mai 14 14:35:04 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:04 Arch-PC kernel: audit: type=1130 audit(1589477704.955:220): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC audit[3052]: USER_AUTH pid=3052 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC kernel: audit: type=1100 audit(1589477709.632:221): pid=3052 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC audit[3052]: USER_ACCT pid=3052 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC audit[3052]: CRED_ACQ pid=3052 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC kernel: audit: type=1101 audit(1589477709.659:222): pid=3052 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC kernel: audit: type=1103 audit(1589477709.659:223): pid=3052 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC kernel: audit: type=1006 audit(1589477709.659:224): pid=3052 uid=0 old-auid=4294967295 auid=1003 tty=tty3 old-ses=4294967295 ses=9 res=1
mai 14 14:35:09 Arch-PC login[3052]: pam_unix(login:session): session opened for user stalker by LOGIN(uid=0)
mai 14 14:35:09 Arch-PC systemd[1]: Created slice User Slice of UID 1003.
mai 14 14:35:09 Arch-PC systemd[1]: Starting User Runtime Directory /run/user/1003...
mai 14 14:35:09 Arch-PC systemd-logind[499]: New session 9 of user stalker.
mai 14 14:35:09 Arch-PC systemd[1]: Finished User Runtime Directory /run/user/1003.
mai 14 14:35:09 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC systemd[1]: Starting User Manager for UID 1003...
mai 14 14:35:09 Arch-PC kernel: audit: type=1130 audit(1589477709.689:225): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC audit[3056]: USER_ACCT pid=3056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC audit[3056]: CRED_ACQ pid=3056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:35:09 Arch-PC systemd[3056]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[stalker] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:35:09 Arch-PC systemd[3056]: pam_unix(systemd-user:session): session opened for user stalker by (uid=0)
mai 14 14:35:09 Arch-PC audit[3056]: USER_START pid=3056 uid=0 auid=1003 ses=10 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC kernel: audit: type=1101 audit(1589477709.695:226): pid=3056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC kernel: audit: type=1103 audit(1589477709.695:227): pid=3056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 14:35:09 Arch-PC kernel: audit: type=1006 audit(1589477709.695:228): pid=3056 uid=0 old-auid=4294967295 auid=1003 tty=(none) old-ses=4294967295 ses=10 res=1
mai 14 14:35:09 Arch-PC kernel: audit: type=1105 audit(1589477709.695:229): pid=3056 uid=0 auid=1003 ses=10 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC audit: AUDIT1334 prog-id=39 op=LOAD
mai 14 14:35:09 Arch-PC audit: AUDIT1334 prog-id=39 op=UNLOAD
mai 14 14:35:09 Arch-PC kernel: audit: type=1334 audit(1589477709.702:230): prog-id=39 op=LOAD
mai 14 14:35:09 Arch-PC systemd[3056]: Reached target Paths.
mai 14 14:35:09 Arch-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:09 Arch-PC audit[3052]: USER_START pid=3052 uid=0 auid=1003 ses=9 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC audit[3052]: CRED_REFR pid=3052 uid=0 auid=1003 ses=9 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="stalker" exe="/usr/bin/login" hostname=Arch-PC addr=? terminal=tty3 res=success'
mai 14 14:35:09 Arch-PC systemd[3056]: Reached target Timers.
mai 14 14:35:09 Arch-PC login[3052]: LOGIN ON tty3 BY stalker
mai 14 14:35:09 Arch-PC systemd[3056]: Starting D-Bus User Message Bus Socket.
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on GnuPG network certificate management daemon.
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on p11-kit server.
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on Multimedia System.
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on Sound System.
mai 14 14:35:09 Arch-PC systemd[3056]: Listening on D-Bus User Message Bus Socket.
mai 14 14:35:09 Arch-PC systemd[3056]: Reached target Sockets.
mai 14 14:35:09 Arch-PC systemd[3056]: Reached target Basic System.
mai 14 14:35:09 Arch-PC systemd[1]: Started User Manager for UID 1003.
mai 14 14:35:09 Arch-PC systemd[3056]: Starting Update XDG user dir configuration...
mai 14 14:35:09 Arch-PC systemd[3056]: xdg-user-dirs-update.service: Succeeded.
mai 14 14:35:09 Arch-PC systemd[3056]: Finished Update XDG user dir configuration.
mai 14 14:35:09 Arch-PC systemd[3056]: Reached target Main User Target.
mai 14 14:35:09 Arch-PC systemd[3056]: Startup finished in 106ms.
mai 14 14:35:09 Arch-PC systemd[1]: Started Session 9 of user stalker.
mai 14 14:35:10 Arch-PC systemd[1]: Stopping User Manager for UID 120...
mai 14 14:35:10 Arch-PC systemd[1941]: Stopped target Main User Target.
mai 14 14:35:10 Arch-PC systemd[1941]: Stopping D-Bus User Message Bus...
mai 14 14:35:10 Arch-PC systemd[1941]: dbus.service: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Stopped D-Bus User Message Bus.
mai 14 14:35:10 Arch-PC systemd[1941]: Stopped target Basic System.
mai 14 14:35:10 Arch-PC systemd[1941]: Stopped target Paths.
mai 14 14:35:10 Arch-PC systemd[1941]: Stopped target Sockets.
mai 14 14:35:10 Arch-PC systemd[1941]: Stopped target Timers.
mai 14 14:35:10 Arch-PC systemd[1941]: dbus.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed D-Bus User Message Bus Socket.
mai 14 14:35:10 Arch-PC systemd[1941]: dirmngr.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed GnuPG network certificate management daemon.
mai 14 14:35:10 Arch-PC systemd[1941]: gpg-agent-browser.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 14 14:35:10 Arch-PC systemd[1941]: gpg-agent-extra.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
mai 14 14:35:10 Arch-PC systemd[1941]: gpg-agent-ssh.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed GnuPG cryptographic agent (ssh-agent emulation).
mai 14 14:35:10 Arch-PC systemd[1941]: gpg-agent.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed GnuPG cryptographic agent and passphrase cache.
mai 14 14:35:10 Arch-PC systemd[1941]: p11-kit-server.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed p11-kit server.
mai 14 14:35:10 Arch-PC systemd[1941]: pipewire.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed Multimedia System.
mai 14 14:35:10 Arch-PC systemd[1941]: pulseaudio.socket: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Closed Sound System.
mai 14 14:35:10 Arch-PC systemd[1941]: Reached target Shutdown.
mai 14 14:35:10 Arch-PC systemd[1941]: systemd-exit.service: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1941]: Finished Exit the Session.
mai 14 14:35:10 Arch-PC systemd[1941]: Reached target Exit the Session.
mai 14 14:35:10 Arch-PC systemd[1942]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
mai 14 14:35:10 Arch-PC systemd[1]: user@120.service: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1]: Stopped User Manager for UID 120.
mai 14 14:35:10 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:10 Arch-PC systemd[1]: Stopping User Runtime Directory /run/user/120...
mai 14 14:35:10 Arch-PC systemd[2954]: run-user-120.mount: Succeeded.
mai 14 14:35:10 Arch-PC systemd[3056]: run-user-120.mount: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1]: run-user-120.mount: Succeeded.
mai 14 14:35:10 Arch-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 14 14:35:10 Arch-PC systemd[1]: user-runtime-dir@120.service: Succeeded.
mai 14 14:35:10 Arch-PC systemd[1]: Stopped User Runtime Directory /run/user/120.
mai 14 14:35:10 Arch-PC systemd[1]: Removed slice User Slice of UID 120.
mai 14 14:35:25 Arch-PC audit[3074]: USER_AUTH pid=3074 uid=1003 auid=1003 ses=9 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC audit[3074]: USER_ACCT pid=3074 uid=1003 auid=1003 ses=9 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC sudo[3074]: stalker : TTY=tty3 ; PWD=/home/stalker ; USER=root ; COMMAND=/usr/bin/journalctl -b --no-pager
mai 14 14:35:25 Arch-PC audit[3074]: CRED_REFR pid=3074 uid=0 auid=1003 ses=9 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC kernel: kauditd_printk_skb: 6 callbacks suppressed
mai 14 14:35:25 Arch-PC kernel: audit: type=1100 audit(1589477725.259:237): pid=3074 uid=1003 auid=1003 ses=9 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC kernel: audit: type=1101 audit(1589477725.259:238): pid=3074 uid=1003 auid=1003 ses=9 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="stalker" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC kernel: audit: type=1110 audit(1589477725.259:239): pid=3074 uid=0 auid=1003 ses=9 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC sudo[3074]: pam_unix(sudo:session): session opened for user root by stalker(uid=0)
mai 14 14:35:25 Arch-PC audit[3074]: USER_START pid=3074 uid=0 auid=1003 ses=9 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'
mai 14 14:35:25 Arch-PC kernel: audit: type=1105 audit(1589477725.262:240): pid=3074 uid=0 auid=1003 ses=9 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=Arch-PC addr=? terminal=/dev/tty3 res=success'Last edited by Strangiato (2020-05-14 18:41:04)
Offline
Run any Qt application with QT_DEBUG_PLUGINS=1 from a terminal and post the output
Offline
Here is the output of "QT_DEBUG_PLUGINS=1 kate"
QFactoryLoader::QFactoryLoader() checking directory path "/usr/lib/qt/plugins/platforms" ...
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/KWinQpaPlugin.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-org.kde.kwin.qpa"
]
},
"archreq": 0,
"className": "KWinIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("wayland-org.kde.kwin.qpa")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libdxcb.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libdxcb.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"xcb",
"dxcb"
]
},
"archreq": 0,
"className": "DPlatformIntegrationPlugin",
"debug": false,
"version": 331264
}
Got keys from plugin meta data ("xcb", "dxcb")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqeglfs.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqeglfs.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"eglfs"
]
},
"archreq": 0,
"className": "QEglFSIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("eglfs")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqlinuxfb.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqlinuxfb.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"linuxfb"
]
},
"archreq": 0,
"className": "QLinuxFbIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("linuxfb")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqminimal.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqminimal.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"minimal"
]
},
"archreq": 0,
"className": "QMinimalIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("minimal")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqminimalegl.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqminimalegl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"minimalegl"
]
},
"archreq": 0,
"className": "QMinimalEglIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("minimalegl")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqoffscreen.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqoffscreen.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"offscreen"
]
},
"archreq": 0,
"className": "QOffscreenIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("offscreen")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqvnc.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqvnc.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"vnc"
]
},
"archreq": 0,
"className": "QVncIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("vnc")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqwayland-egl.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqwayland-egl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-egl"
]
},
"archreq": 0,
"className": "QWaylandEglPlatformIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("wayland-egl")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqwayland-generic.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqwayland-generic.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland"
]
},
"archreq": 0,
"className": "QWaylandIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("wayland")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqwayland-xcomposite-egl.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqwayland-xcomposite-egl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-xcomposite-egl"
]
},
"archreq": 0,
"className": "QWaylandXCompositeEglPlatformIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("wayland-xcomposite-egl")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqwayland-xcomposite-glx.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqwayland-xcomposite-glx.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-xcomposite-glx"
]
},
"archreq": 0,
"className": "QWaylandXCompositeGlxPlatformIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("wayland-xcomposite-glx")
QFactoryLoader::QFactoryLoader() looking at "/usr/lib/qt/plugins/platforms/libqxcb.so"
Found metadata in lib /usr/lib/qt/plugins/platforms/libqxcb.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"xcb"
]
},
"archreq": 0,
"className": "QXcbIntegrationPlugin",
"debug": false,
"version": 331520
}
Got keys from plugin meta data ("xcb")
QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" ...
Cannot load library /usr/lib/qt/plugins/platforms/libdxcb.so: (/usr/lib/qt/plugins/platforms/libdxcb.so: undefined symbol: _ZN10QXcbWindow17startSystemResizeERK6QPointN2Qt6CornerE, version Qt_5_PRIVATE_API)
QLibraryPrivate::loadPlugin failed on "/usr/lib/qt/plugins/platforms/libdxcb.so" : "Cannot load library /usr/lib/qt/plugins/platforms/libdxcb.so: (/usr/lib/qt/plugins/platforms/libdxcb.so: undefined symbol: _ZN10QXcbWindow17startSystemResizeERK6QPointN2Qt6CornerE, version Qt_5_PRIVATE_API)"
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.Offline
Remove deepin-qt5dxcb-plugin
Offline
I had to uninstall three packages: deepin-qt5dxcb-plugin, deepin-qt5integration and deepin-music
Problem solved.
Thank you Antonio.
Offline