From lapointe.jonathan at gmail.com Sat Dec 1 02:41:28 2018 From: lapointe.jonathan at gmail.com (Jonathan Lapointe) Date: Fri, 30 Nov 2018 21:41:28 -0500 Subject: [Assist] qemu hotplug usb Message-ID: <1543632088.1249.0@smtp.gmail.com> Is there a way to do hotplug usb device with qemu. I would like to do that with guest VM. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill-auger at peers.community Sat Dec 1 06:09:18 2018 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Dec 2018 01:09:18 -0500 Subject: [Assist] Strange sound problem In-Reply-To: <1543596355.1497.0@smtp.gmail.com> References: <1543522774.4741.0@smtp.gmail.com> <1543596355.1497.0@smtp.gmail.com> Message-ID: <20181201010918.5f12d647@parabola> On Fri, 30 Nov 2018 11:45:55 -0500 Jonathan wrote: > Usualy there is a way for to select on what I want to hear it. > (Gaming headset or built-in audio analog stereo). (pavucontrol) > For some reason with qemu (with pa), it doesnt offer me this choice. pavucontrol would normally work as you expect except it seems your qemu configuration is using the USB sound card exclusively, preventing pulse from using it - unless real-time latency is a high concern, there of no noticeable benefit of pass-through for a sound card On Fri, 30 Nov 2018 11:45:55 -0500 Jonathan wrote: > I would like to be able to hear in my gaming headset every other > thing, not just what is happening in my vm. this also would normally work as you expect if you let qemu handle the sound output - that becomes simply another pulse client on the host (if that's your thing) On Fri, 30 Nov 2018 21:09:52 +0000 grizzlyuser wrote: > If that's the case, then to output the audio from both the host and > the guest using the same headset, you just have to use some virtual > audio device, and select the headset in the host as the default audio > device. "-soundhw ac97" is already present in the script, so it seems > to be sufficient. or, more simply, remove the pass-through and let qemu "just work" by default or, for more sophisticated needs, use the net-device features of pulse (or JACK, if low-latency is a concern) From bill-auger at peers.community Sat Dec 1 06:15:58 2018 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Dec 2018 01:15:58 -0500 Subject: [Assist] qemu hotplug usb In-Reply-To: <1543632088.1249.0@smtp.gmail.com> References: <1543632088.1249.0@smtp.gmail.com> Message-ID: <20181201011558.6065cba7@parabola> you have been asking many questions about qemu - most such questions are not specific to parabola but would be best answered by the qemu folks - qemu has mailing lists and an IRC channel too - are you asking them these questions also? - is their tech support in-adequate? regarding this particular question, the answer is probably in the docs - you can do many magical things in the qemu command shell - none of which i remember off-hand - the qemu website has thorough docs with a section for those commands From lapointe.jonathan at gmail.com Sat Dec 1 14:01:12 2018 From: lapointe.jonathan at gmail.com (Jonathan Lapointe) Date: Sat, 01 Dec 2018 09:01:12 -0500 Subject: [Assist] Strange sound problem In-Reply-To: References: <1543522774.4741.0@smtp.gmail.com> <1543596355.1497.0@smtp.gmail.com> Message-ID: <1543672872.2954.0@smtp.gmail.com> Finally, I take my pass-throught (usb headset) from my script. I let my webcam on, this one has microphone inside so it can usefull if I don't use the microphone on my gaming headset. Sound seem fine eventought the microphone is on my webcam. By removing the pass-throught that did fix the problem, i have with not having all sound from my desktop inside my headset. On Sat, Dec 1, 2018 at 1:09 AM, bill-auger wrote: > On Fri, 30 Nov 2018 11:45:55 -0500 Jonathan wrote: >> Usualy there is a way for to select on what I want to hear it. >> (Gaming headset or built-in audio analog stereo). (pavucontrol) >> For some reason with qemu (with pa), it doesnt offer me this choice. > > pavucontrol would normally work as you expect except it seems your > qemu > configuration is using the USB sound card exclusively, preventing > pulse > from using it - unless real-time latency is a high concern, there of > no noticeable benefit of pass-through for a sound card > > > On Fri, 30 Nov 2018 11:45:55 -0500 Jonathan wrote: >> I would like to be able to hear in my gaming headset every other >> thing, not just what is happening in my vm. > > this also would normally work as you expect if you let qemu handle the > sound output - that becomes simply another pulse client on the host > (if that's your thing) > > > On Fri, 30 Nov 2018 21:09:52 +0000 grizzlyuser wrote: >> If that's the case, then to output the audio from both the host and >> the guest using the same headset, you just have to use some virtual >> audio device, and select the headset in the host as the default >> audio >> device. "-soundhw ac97" is already present in the script, so it >> seems >> to be sufficient. > > or, more simply, remove the pass-through and let qemu "just work" by > default > > or, for more sophisticated needs, use the net-device features of pulse > (or JACK, if low-latency is a concern) > > > > _______________________________________________ > Assist mailing list > Assist at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/assist -------------- next part -------------- An HTML attachment was scrubbed... URL: From megver83 at hyperbola.info Sat Dec 1 19:12:37 2018 From: megver83 at hyperbola.info (Megver83) Date: Sat, 1 Dec 2018 16:12:37 -0300 Subject: [Assist] qemu hotplug usb In-Reply-To: <1543632088.1249.0@smtp.gmail.com> References: <1543632088.1249.0@smtp.gmail.com> Message-ID: <88a6c391-b8e7-3605-fd40-1dbf88204473@hyperbola.info> El 30/11/18 a las 23:41, Jonathan Lapointe escribi?: > Is there a way to do hotplug usb device with qemu. ?I would like to do > that with guest VM. > > > _______________________________________________ > Assist mailing list > Assist at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/assist > I'm using aqemu to manage my QEMU VMs, and it has an option to manage physical usb ports so they can appear in your VM. -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: pixelfed.social/Megver83 PeerTube: peertube.xtenz.xyz/accounts/megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Sun Dec 2 00:36:45 2018 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Dec 2018 19:36:45 -0500 Subject: [Assist] qemu hotplug usb In-Reply-To: <88a6c391-b8e7-3605-fd40-1dbf88204473@hyperbola.info> References: <1543632088.1249.0@smtp.gmail.com> <88a6c391-b8e7-3605-fd40-1dbf88204473@hyperbola.info> Message-ID: <20181201193645.5fbee6bb@parabola> On Sat, 1 Dec 2018 16:12:37 -0300 Megver83 wrote: > I'm using aqemu to manage my QEMU VMs, and it has an option to manage > physical usb ports so they can appear in your VM. Jonathan wants to plug/unplug the USB device repeatedly while the guest is running, and watch `lsusb` changes in the live guest - can aqemu do that? From jonathan.lapointe.07 at videotron.ca Sun Dec 2 00:40:38 2018 From: jonathan.lapointe.07 at videotron.ca (Jonathan Lapointe) Date: Sat, 01 Dec 2018 19:40:38 -0500 Subject: [Assist] qemu hotplug usb In-Reply-To: References: <1543632088.1249.0@smtp.gmail.com> <88a6c391-b8e7-3605-fd40-1dbf88204473@hyperbola.info> Message-ID: <1543711238.944.0@smtp.videotron.ca> it was for the usb headset, but i was confused. I try aqemu but found it a bit useless for what i have already done. On Sat, Dec 1, 2018 at 7:36 PM, bill-auger wrote: > On Sat, 1 Dec 2018 16:12:37 -0300 Megver83 wrote: >> I'm using aqemu to manage my QEMU VMs, and it has an option to >> manage >> physical usb ports so they can appear in your VM. > > Jonathan wants to plug/unplug the USB device repeatedly while the > guest > is running, and watch `lsusb` changes in the live guest - can aqemu do > that? > _______________________________________________ > Assist mailing list > Assist at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/assist -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill-auger at peers.community Sun Dec 2 01:01:48 2018 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Dec 2018 20:01:48 -0500 Subject: [Assist] Strange sound problem In-Reply-To: <1543672872.2954.0@smtp.gmail.com> References: <1543522774.4741.0@smtp.gmail.com> <1543596355.1497.0@smtp.gmail.com> <1543672872.2954.0@smtp.gmail.com> Message-ID: <20181201200148.38e88c45@parabola> Jonathan - i dont quite understand everything in that last post - are you saying that your sound is all working as you expect and you are satisfied? - or do you still have some trouble? - again, this issue is probably not peculiar to parabola, so the upstream program support is probably best able to help with using that program in detail - i would expect such an important program as pulseaudio to have very good user support assuming you want pulse audio and want to use only your headphones for all sound, it should be this simple: * if that one device is your headphones, reboot and disable the PC internal sound card in your BIOS setting - or otherwise, boot your computer with one sound card device * ensure pulse is running and all your normal desktop sound are working as expected * start qemu without USB passthrough on its audio device * qemu should be a normal pulseaudio client seen in pavucontrol on the host - mixed with the host sounds * if that works as expected, you can experiment with multiple sound card if you want to From lapointe.jonathan at gmail.com Sun Dec 2 01:50:55 2018 From: lapointe.jonathan at gmail.com (lapointe.jonathan) Date: Sat, 01 Dec 2018 20:50:55 -0500 Subject: [Assist] Strange sound problem Message-ID: <3a3waem40en8q7y0i5d9nfmi.1543715072892@email.android.com> Hi Bill, these last few days i been deeling with pulseaudio who was giving me headache about sound in qemu to my headphone but outside qemu sound was redirected to my speaker. Pavucontrol was not letting choice between headphone or speaker. I found ou that the problem was the way i was passing my headset to my vm guest. I change it and that did fix my problem. I tought i will be missing the microphone on my headset but then it was not the case because i found out the microphone on my webcam was sufficient. So i have my headset working half but with my microphone from my webcam am ok. So i can now have all sound from anywhere redirected to my headphone. -------- Message d'origine -------- De : bill-auger Date : 01/12/2018 20:01 (GMT-05:00) ? : assist at lists.parabola.nu Objet : Re: [Assist] Strange sound problem Jonathan - i dont quite understand everything in that last post - are you saying that your sound is all working as you expect and you are satisfied? - or do you still have some trouble? - again, this issue is probably not peculiar to parabola, so the upstream program support is probably best able to help with using that program in detail - i would expect such an important program as pulseaudio to have very good user support assuming you want pulse audio and want to use only your headphones for all sound, it should be this simple: * if that one device is your headphones, reboot and disable the PC internal sound card in your BIOS setting - or otherwise, boot your computer with one sound card device * ensure pulse is running and all your normal desktop sound are working as expected * start qemu without USB passthrough on its audio device * qemu should be a normal pulseaudio client seen in pavucontrol on the host - mixed with the host sounds * if that works as expected, you can experiment with multiple sound card if you want to _______________________________________________ Assist mailing list Assist at lists.parabola.nu https://lists.parabola.nu/mailman/listinfo/assist -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.lapointe.07 at videotron.ca Sun Dec 2 12:37:47 2018 From: jonathan.lapointe.07 at videotron.ca (Jonathan Lapointe) Date: Sun, 02 Dec 2018 07:37:47 -0500 Subject: [Assist] dual monitor Message-ID: <1543754267.5906.0@smtp.videotron.ca> I would like to know if there is a way to have a application in fullscreen in one monitor and still be able to use the second monitor for other thing? -------------- next part -------------- An HTML attachment was scrubbed... URL: From lapointe.jonathan at gmail.com Sun Dec 2 15:07:58 2018 From: lapointe.jonathan at gmail.com (Jonathan Lapointe) Date: Sun, 02 Dec 2018 10:07:58 -0500 Subject: [Assist] dual monitor In-Reply-To: References: Message-ID: <1543763278.2159.0@smtp.gmail.com> I fix the problem. I add -display sdl to qemu and it was fix (almost)...with -vga virtio enabled, I was able to have qemu in fullscreen and at the same be able to change monitors. I had to remove titlebar (xfce tweak) but then it was perfect. On Sun, Dec 2, 2018 at 7:37 AM, Jonathan Lapointe wrote: > I would like to know if there is a way to have a application in > fullscreen in one monitor and still be able to use the second monitor > for other thing? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mazocomp at disroot.org Mon Dec 3 16:53:06 2018 From: mazocomp at disroot.org (Leonid Bobrov) Date: Mon, 3 Dec 2018 18:53:06 +0200 Subject: [Assist] [cwm] Minimalistic keyboard-friendly window manager Message-ID: <20181203165306.GA24036@parabola.lan> https://aur.archlinux.org/packages/cwm/ It also has effective mouse key bindings, easy to configure via cwmrc(5) and is ISC licensed. From GNUtoo at cyberdimension.org Tue Dec 4 18:42:19 2018 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Tue, 4 Dec 2018 19:42:19 +0100 Subject: [Assist] dual monitor In-Reply-To: <1543763278.2159.0@smtp.gmail.com> References: <1543763278.2159.0@smtp.gmail.com> Message-ID: <20181204194219.1030d016@primary_laptop.localdomain> On Sun, 02 Dec 2018 10:07:58 -0500 Jonathan Lapointe wrote: > I fix the problem. I add -display sdl to qemu and it was fix > (almost)...with -vga virtio enabled, I was able to have qemu in > fullscreen and at the same be able to change monitors. I had to > remove titlebar (xfce tweak) but then it was perfect. If you use xfce, look in the panel settings: you can set "Output" to the monitor you want. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Wed Dec 5 01:10:42 2018 From: bill-auger at peers.community (bill-auger) Date: Tue, 4 Dec 2018 20:10:42 -0500 Subject: [Assist] dual monitor In-Reply-To: <20181204194219.1030d016@primary_laptop.localdomain> References: <1543763278.2159.0@smtp.gmail.com> <20181204194219.1030d016@primary_laptop.localdomain> Message-ID: <20181204201042.04acb0a0@parabola> indeed, the WM is your friend on this one - with openbox, you can make such preferences permanent, just by adding an XML entry like: 3 true From jonathan.lapointe.07 at videotron.ca Tue Dec 11 01:00:44 2018 From: jonathan.lapointe.07 at videotron.ca (Jonathan Lapointe) Date: Mon, 10 Dec 2018 20:00:44 -0500 Subject: [Assist] nouveau FREEZE Message-ID: <1544490044.2209.0@smtp.videotron.ca> I keep having the same problem, my system freeze and it happen suddently. in my journalctl (log), i can read: Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: write fault at 0000240000 engine 00 [GR] client 0f [GPC0/PROP_0] reason 02 [PTE] on channel 2 [007fb4a000 Xorg[600]] Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: channel 2: killed Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: engine 6: scheduled for recovery Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: Xorg[600]: channel 2 killed! It happen to me already 3 times, 2 time on 7 december (am/pm) et one time on 10 december (pm) I think it may be my videocard so I just today remove it, and will try tomorrow. If for the next day i don't have problem it will be the fault of videocard otherwise it is something i forgot to put somewhere so nouveau stop doing this... here an example: http://pasteall.org/pic/42e3b1d8d0776694adf929a6799a96b7 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GNUtoo at cyberdimension.org Tue Dec 11 14:15:45 2018 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Tue, 11 Dec 2018 15:15:45 +0100 Subject: [Assist] nouveau FREEZE In-Reply-To: <1544490044.2209.0@smtp.videotron.ca> References: <1544490044.2209.0@smtp.videotron.ca> Message-ID: <20181211151545.455cd98c@primary_laptop.localdomain> On Mon, 10 Dec 2018 20:00:44 -0500 Jonathan Lapointe wrote: > I keep having the same problem, my system freeze and it happen > suddently. > > in my journalctl (log), i can read: > > Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: write fault > at 0000240000 engine 00 [GR] client 0f [GPC0/PROP_0] reason 02 [PTE] > on channel 2 [007fb4a000 Xorg[600]] > Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: channel 2: > killed > Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: runlist 0: > scheduled for recovery > Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: engine 0: > scheduled for recovery > Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: fifo: engine 6: > scheduled for recovery > Dec 10 14:41:52 m81 kernel: nouveau 0000:01:00.0: Xorg[600]: channel > 2 killed! > > It happen to me already 3 times, 2 time on 7 december (am/pm) et one > time on 10 december (pm) > > I think it may be my videocard so I just today remove it, and will > try tomorrow. If for the next day i don't have problem it will be the > fault of videocard otherwise it is something i forgot to put > somewhere so nouveau stop doing this... > > here an example: > http://pasteall.org/pic/42e3b1d8d0776694adf929a6799a96b7 Having the log is the first step to fix that. I don't know if there are any Nouveau developers on this mailing list, so the next step could be to: 1) Look if there is already a bugreport for the same issue for nouveau in nouveau bug tracker. Since you have the logs, you can search there with strings found in your logs such as "fifo: write fault at" 2) If no similar bug exists, try to bugreport there. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From uaqben at disroot.org Fri Dec 14 19:04:01 2018 From: uaqben at disroot.org (Ben) Date: Fri, 14 Dec 2018 20:04:01 +0100 Subject: [Assist] Problem with coreboot vs libreboot Message-ID: <808df565-8dad-778d-f8ba-dd29a02a173d@disroot.org> Hi All, I've been using Parabola, very happily, with Libreboot for a couple of years appx. Recently, I got a second machine, Thinkpad x230, and compiled my first coreboot rom, with GRUB as payload. Flashed the x230, and all good. I added a small msata to the x230; installed antergos (to go fast) for work I'm required to use things like slack :( I also replaced the wifi for another atheros. So, instead of lugging two laptops around, I'd like to have my parabola running on the x230 too. The odd thing I have is that I can't get the x230 to unlock and boot my parabola drive (ie. taking it out of x200, and putting it in x230). coreboot can unlock & boot antergos (lvm / luks; though /boot is not encrypted) but coreboot fails to unlock my parabola drive. I tested installing a fresh parabola on a different hdd in the x230, but same problem. As my x200 parabola runs with GPT, two partitions (swap, and then a BTRFS volume), and the Antergos install is MBR (swap & EXT4). I tested fresh parabola install both running off BTRFS and EXT4. No difference. Trying to see if the problem is due to coreboot's grub's support for GPT, I searched, and realized that I hadn't added `gptsync` in the coreboot config for GRUB payload. Whereas this module is included in Libreboot. I rebuilt another coreboot rom with `gptsync` (it already had `part_gpt`), but same result. Last idea I have, is maybe I need to add a GRUB module for the `whirlpool` encryption (ie. from Parabola wiki install w/ Libreboot; and same recommendation on libreboot.org's install parabola document) I can give more (precise) info, anything required to understand/help me troubleshoot this -- but first I think I should ask if this mailing list is appropriate for my problem.. or if I should rather ask for help from libreboot and/or coreboot projects. I think people here have Parabola running off both libreboot & coreboot machines -- so that's why I thought a good idea to ask for help here first. Thanks! Ben From bill-auger at peers.community Fri Dec 14 21:08:16 2018 From: bill-auger at peers.community (bill-auger) Date: Fri, 14 Dec 2018 16:08:16 -0500 Subject: [Assist] Problem with coreboot vs libreboot In-Reply-To: <808df565-8dad-778d-f8ba-dd29a02a173d@disroot.org> References: <808df565-8dad-778d-f8ba-dd29a02a173d@disroot.org> Message-ID: <20181214160816.167449bd@parabola> On Fri, 14 Dec 2018 20:04:01 +0100 Ben wrote: > I should ask if this > mailing list is appropriate for my problem.. or if I should rather > ask for help from libreboot and/or coreboot projects. > > I think people here have Parabola running off both libreboot & > coreboot machines it is, and yes some people do - from my experience, most libreboot users have no trouble installing parabola; but there has always been some people who have trouble with libreboot and parabola, mostly with the LiveISOs; but we do not know why that is yet - there is an open issue about that on the bug tracker now https://labs.parabola.nu/issues/2108 i think the biggest hurdle here is that no parabola devs have a computer with libreboot on it; so it would take some co-operation from users like yourself who can actually demonstrate the problem and are willing to spend some time experimenting - that is the real blocker for the bug ticket above - unless the OP or another libreboot user steps up to be the guinea-pig, the root of the problem may never be found frankly the first logical trouble-shooting step in this case is to re-flash your BIOS back to the factory default and verify that parabola is actually installed properly and that the standard GRUB can boot it - then perhaps next re-install parabola with no encryption on a single partition and try booting that with the libreboot GRUB - you would not need to keep it that way o/c - this is just basic trouble-shooting to isolate the cause from the complexity - o/c people generally do not like that suggestion; but the fact is, there is quite a lot of complexity in a system with libreboot+luks+multiple-partitions, and the more complexity there is, the more things that can go wrong; and isolating the problem is exponentially more difficult if one insists on testing only the most complex desired configuration - i suspect that the libreboot users who have no trouble with parabola, are those who installed in a more humble configuration (e.g. an MBR partition table, or a single partition, or no encryption, or using legacy BIOS) - thats just a guess though i can not recall anyone having a problem with coreboot specifically; but i think that intersection is quite small, especially if constrained to that one single model of computer - you would probably be wise to CC this thread to coreboot or libreboot (whichever you want to use) in order to reach more users who are running parabola with the same computer model From GNUtoo at cyberdimension.org Tue Dec 18 14:31:45 2018 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Tue, 18 Dec 2018 15:31:45 +0100 Subject: [Assist] Problem with coreboot vs libreboot In-Reply-To: <808df565-8dad-778d-f8ba-dd29a02a173d@disroot.org> References: <808df565-8dad-778d-f8ba-dd29a02a173d@disroot.org> Message-ID: <20181218153145.2faaea00@primary_laptop.localdomain> On Fri, 14 Dec 2018 20:04:01 +0100 Ben wrote: > Hi All, Hi, > The odd thing I have is that I can't get the x230 to unlock and boot > my parabola drive (ie. taking it out of x200, and putting it in x230). > > coreboot can unlock & boot antergos (lvm / luks; though /boot is not > encrypted) > > but coreboot fails to unlock my parabola drive. in make menuconfig you can configure which modules are included and autoloaded in the grub payload. Here's an example of modules that might work: GRUB CONFIG_GRUB2_EXTRA_MODULES="acpi ahci all_video archelp ata at_keyboard blocklist boot boottime btrfs cat cbfs cbls cbmemc cbtime chain cmosdump cmostest cmp configfile cpio cpuid crc64 cryptodisk crypto cs5536 datehook date datetime diskfilter disk div dm_nv echo ehci elf eval exfat ext2 extcmd fat file fshelp gcry_crc gcry_rfc2268 gcry_rijndael gcry_rsa gcry_seed gcry_serpent gcry_sha1 gcry_sha256 gcry_sha512 gcry_twofish gettext gfxmenu gfxterm_background gfxterm_menu gptsync gzio halt hashsum hdparm help hexdump iorw iso9660 jpeg keylayouts keystatus ldm linux16 linux loadenv loopback lsacpi lsmmap ls lspci luks lvm lzopio mda_text memdisk memrw minicmd mmap morse mpi msdospart multiboot2 multiboot nativedisk newc nilfs2 normal odc offsetio ohci part_gpt part_msdos parttool password password_pbkdf2 pata pbkdf2 pcidump pci play priority_queue probe procfs progress random read reboot regexp relocator romfs scsi search_fs_file search_fs_uuid search_label search serial setjmp setpci sfs sleep spkmodem squash4 syslinuxcfg tar terminal terminfo testload test testspeed time trig tr true udf uhci usb_keyboard usb usbms usbserial_common usbserial_ftdi usbserial_pl2303 usbserial_usbdebug verify video_colors videoinfo xzio" Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From dllud at riseup.net Sun Dec 16 06:32:03 2018 From: dllud at riseup.net (dllud) Date: Sun, 16 Dec 2018 06:32:03 -0000 Subject: [Assist] Why does community repo lag behind Arch while extra doesn't? Message-ID: <181068cc-b14b-92cd-4567-8fabd8e03fcc@riseup.net> Hi! I am having issues with incompatible package versions between the 'extra' and 'community' repos. On extra there is qt5 5.12.0, while the qt5-styleplugins package from community is still at version 5.0.0.20170311-8, which was built for a previous qt5 version and is now incompatible. The fixed qt5-styleplugins version (5.0.0.20170311-9) was put into Arch's community repo on the same day as the qt5 upgrade (2018-12-10) but still didn't made it into Parabola What causes this lag? I am using the default /etc/pacman.d/mirrorlist that points to https://redirector.parabola.nu/$repo/os/$arch and https://repomirror.parabola.nu/$repo/os/$arch Regards, dllud