On Thu, 19 Sep 2019 20:12:53 -0500, David C. Rankin wrote:
>All,
>
> Note to anyone is still using Virtualbox 5.2.32 (that can't move to
> Ver. 6
>due to headless behavior with Windows guests), on update to Linux 5.3,
>virtualbox models fail to build using dkms.
>
>Upstream bug filed: https://www.
"David C. Rankin" on Thu, 2019/09/19 20:12:
> All,
>
> Note to anyone is still using Virtualbox 5.2.32 (that can't move to Ver. 6
> due to headless behavior with Windows guests), on update to Linux 5.3,
> virtualbox models fail to build using dkms.
>
> Upstream bug filed: https://www.virtualbo
All,
Note to anyone is still using Virtualbox 5.2.32 (that can't move to Ver. 6
due to headless behavior with Windows guests), on update to Linux 5.3,
virtualbox models fail to build using dkms.
Upstream bug filed: https://www.virtualbox.org/ticket/18949
(make.log attached to bug report)
--
Hello,
** Amish via arch-general [2019-09-20 05:59:11 +0530]:
> On 19/09/19 10:44 pm, Eli Schwartz via arch-general wrote:
>> On September 19, 2019 1:00:26 PM EDT, Amish via arch-general
>> wrote:
>>> those users who use logwatch that they need to take following actions:
>>>
>>> 1) pacman -Syu
On 19/09/19 10:44 pm, Eli Schwartz via arch-general wrote:
On September 19, 2019 1:00:26 PM EDT, Amish via arch-general
wrote:
those users who use logwatch that they need to take following actions:
1) pacman -Syu
2) cat /usr/lib/systemd/system/logwatch.service.d/local.conf
[Service]
ExecSt
On September 19, 2019 1:00:26 PM EDT, Amish via arch-general
wrote:
> Hello,
>
> Recently logwatch package was updated.
>
> The cron file (from cron.daily) was removed and replaced with
> systemd.timer.
>
> But logwatch.timer is not activated automatically, which means the
> users
> who use l
Hello,
Recently logwatch package was updated.
The cron file (from cron.daily) was removed and replaced with systemd.timer.
But logwatch.timer is not activated automatically, which means the users
who use logwatch will stop getting daily "auditing" emails and may not
realize this for some days
For some GPU stress-tests you may use furmark, it's provided by `gputest`
in AUR.
чт, 19 вер. 2019, 19:23 користувач L. Rose пише:
>
>
> On 19 September 2019 17:29:05 CEST, hw wrote:
> >
> >At least NVIDIA graphics cards can go bad in that they can cause
> >temporary
> >hangs, accompanied by lo
On 19 September 2019 17:29:05 CEST, hw wrote:
>
>At least NVIDIA graphics cards can go bad in that they can cause
>temporary
>hangs, accompanied by log messages, indicating that the GPU is damaged.
Where would I find such logs? I couldn't find anything in dmesg so far.
>So perhaps if you wer
On Thursday, 19 September 2019 11:37:34 CEST LuKaRo wrote:
>[...]
>> glxinfo furthermore says:
>
> Extended renderer info (GLX_MESA_query_renderer):
> Vendor: Intel Open Source Technology Center (0x8086)
> Device: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) (0x1916)
> Version: 19.
> I had an issue like this with KDE having huge lag problems. I checked htop
> and determined it was caused by applications dropping into uninterruptible
> sleep due to I/o wait. That in turn was caused by baloo file indexer
> running rampant in my huge music collection.
Baloo is disabled, I alread
11 matches
Mail list logo
