On Fri, Sep 20, 2019 at 7:33 PM Wells, Roger K. via users <
users@lists.fedoraproject.org> wrote:
> I can't replicate your case exactly, but
>
> The pc is a thinkpad x280
> uname -r: 5.2.9-200.fc30.x86_64
> video adapter is usb-c to vga and cable is vga to the monitor's vga input
> external mo
> On Wed, 2019-10-16 at 17:35 +, sixpack13 wrote:
>
> I wouldn't do that. At this time, /var/tmp is expected to be on
> permanent storage, some things might expect data to remain available.
> Some things might generate more temp files than your RAM (especially if
> you burn DVDs or Blurays
On 16/10/2019 09.18, Marcel Oliver wrote:
I am running Fedora 30 (Cinnamon Spin) on a Dell XPS 13 (9380) laptop.
Until about early August, everything was working perfectly, but then,
with some update, suspend problems developed which I have difficulties
debugging.
Initially, I thought this
On 10/16/19 12:18 AM, Marcel Oliver wrote:
Initially, I thought this is a kernel issue. Kernels up to
5.1.18-300.fc30.x86_64 are working, everything starting from
5.2.6-200.fc30.x86_64 (I did not try anything in between) is failing
in the following way:
5.2 does seem a little broken on the
On Wed, 2019-10-16 at 17:35 +, sixpack13 wrote:
> if you want to have an automatical cleanage for /var/tmp:
> =
> 1. add the following line to your /etc/fstab
>
> "tmpfs /var/tmp tmpfsdefaults,nosuid,nodev,noexec,mode=1777
> 0 0"
>
> - wi
On Tue, 2019-10-15 at 20:48 -0300, George N. White III wrote:
> I think homeplug is designed to recover after power outages.
You'd hope so. As far as I'm concerned, any home appliance that needs
a UPS is badly engineered.
Devices should have enough internal power supply filtering that the
regulu
On 10/17/19 6:15 AM, home user wrote:
I'm having to put this aside until tomorrow afternoon. I have personal
business and commitments this evening and tomorrow morning; I'll do my weekly
incremental back-up; scans, and patches tomorrow midday. (another working
lunch)
Here's what's been acco
On 10/16/2019 04:15 PM, home user wrote:
I'm having to put this aside until tomorrow afternoon. I have personal
business and commitments this evening and tomorrow morning; I'll do my
weekly incremental back-up; scans, and patches tomorrow midday. (another
working lunch)
Have you tried bleach
I'm having to put this aside until tomorrow afternoon. I have personal
business and commitments this evening and tomorrow morning; I'll do my
weekly incremental back-up; scans, and patches tomorrow midday.
(another working lunch)
Here's what's been accomplished so far:
---
-bash.
On 10/17/19 3:11 AM, Samuel Sieb wrote:
On 10/16/19 10:51 AM, sixpack13 wrote:
On 10/16/19 8:33 AM, sixpack13 wrote:
journald is pretty good about cleaning up after itself.
obviously NOT by an size of 4.5 GB (not MB !)
That depends on what you want. I'm happy to have lots of logs, I'v
okay, thanks for clarification !
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidel
> (responding to sixpack13)
...
> But I'm not sure I should do anything that affects current journal
> files, and there are a few. I looked at the man page. Maybe I'm
> incorrectly understanding the --rotate, --update-catalog, and --sync,
> but it looks like it will affect currently active log
On Wed, Oct 16, 2019 at 05:51:16PM -, sixpack13 wrote:
> > journald is pretty good about cleaning up after itself.
> obviously NOT by an size of 4.5 GB (not MB !)
This is because the default is to base the limit on the size and free space
on the filesystem used for the journal. This is ver
On 10/16/19 10:51 AM, sixpack13 wrote:
On 10/16/19 8:33 AM, sixpack13 wrote:
journald is pretty good about cleaning up after itself.
obviously NOT by an size of 4.5 GB (not MB !)
That depends on what you want. I'm happy to have lots of logs, I've run
into situations where the log didn
(responding to Samuel)
> No need. As you can see, most of it is really old.
> You can delete everything in there except the systemd-private* ones.
done.
thanks,
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email t
> On 10/16/19 8:33 AM, sixpack13 wrote:
>
> journald is pretty good about cleaning up after itself.
obviously NOT by an size of 4.5 GB (not MB !)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lis
(responding to sixpack13)
> journal/ 4.5 GB 101
> I do clean up my /var/log/journal/ via following commands (maybe
imperfect !):
> sudo journalctl --flush --rotate;
> sudo rm -rfv /var/log/journal/*/*@*;
> sudo journalctl --update-catalog --sync;
I agree that there's a lot there that can and sho
as I said just one comment before your's.
it is save to do
sudo rm -rf /var/tmp/*
as you can see in /var/tmp/ are mostly old temporary files in:
- they care "tmp" in it's name
- are generated from akmod during compile of your module for your nvidia
graphic card
- the most current files/directori
On 10/16/19 8:33 AM, sixpack13 wrote:
...
"https://paste.fedoraproject.org/paste/0itNgq0umG~nGgd92LZ~kQ";.
journal/ 4.5 GB 101
I do clean up my /var/log/journal/ via following commands (maybe imperfect !):
sudo journalctl --flush --rotate;
sudo rm -rfv /var/log/journ
On 10/16/19 9:36 AM, sixpack13 wrote:
...
"https://paste.fedoraproject.org/paste/0itNgq0umG~nGgd92LZ~kQ";.
/var/tmp/ 1.9 GB 1403
sudo rm -rf /var/tmp/*
I would not recommend that. systemd services use that space for temp
files. You're likely to cause a problem wi
On 10/16/19 9:54 AM, home user wrote:
(responding to Samuel)
> /var/cache/tmp has a lot of space. I don't even have that directory.
What's in there.
I have no such directory. Do you mean "/var/tmp"?
-
bash.57[tmp]: pwd
/var/tmp
bash.58[tmp]: ls -la
total 220
-
I can fpaste an "ls -alR
On 10/16/19 9:29 AM, home user wrote:
(responding to Ed)
> Since you're at F30 you should also have a /var/cache/PackageKit/30
directory structure
> which is now being used.
I don't have it. This might relate to actions taken in my December 2018
thread "unwanted checks for updates". I'd li
(responding to Samuel)
> The first big wins are to delete the 28 and 29 from under PackageKit
done.
> You don't show what's really under /var/cache/yum, but anything under
there can be deleted.
bash.49[yum]: ls -la
-
total 16
drwxr-xr-x. 3 root root 4096 May 21 10:44 .
drwxr-xr-x. 26 r
...
> "https://paste.fedoraproject.org/paste/0itNgq0umG~nGgd92LZ~kQ";.
>
/var/tmp/ 1.9 GB 1403
sudo rm -rf /var/tmp/*
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.f
(responding to Ed)
> So, the 28 is no longer being used and can be removed.
Done.
> Since you're at F30 you should also have a /var/cache/PackageKit/30
directory structure
> which is now being used.
I don't have it. This might relate to actions taken in my December 2018
thread "unwanted check
Hi
I have recently put together a new machine using
an RX 5700 XT graphics card & X570 motherboard.
I have been using it for about a month.
My understanding is that kernel 5.3 provides "fuller" support for RX 5700
graphics
With the 5.2 kernel (eg 5.2.18-200.fc30.x86_64) it has been working fine.
...
> "https://paste.fedoraproject.org/paste/0itNgq0umG~nGgd92LZ~kQ";.
>
journal/ 4.5 GB 101
I do clean up my /var/log/journal/ via following commands (maybe imperfect !):
sudo journalctl --flush --rotate;
sudo rm -rfv /var/log/journal/*/*@*;
sudo journalctl --update-catalog
On 10/16/19 1:15 AM, Patrick O'Callaghan wrote:
On Tue, 2019-10-15 at 19:06 -0700, ToddAndMargo via users wrote:
How they get baobab out of "Gnome Disk Analyzer" is beyond me.
Whimsical names are Linux (and especially GNU) tradition. The baobab is
a tree with a complex root system, so it's app
...
s/for that case ! /for that case ! AND Backups of your important data/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/
> (responding to sixpack13)
> This is workstation in my home; I am
> it's sole user;
That's what I was assuming.
it was just a rhetorical question !
> ... But I've been unemployed for 5+ years, so I have no
> realistic alternative but to be my own sys. admin. ...
you shouldn't feel neither s
> On 10/15/2019 03:05 PM, sixpack13 wrote:
>
> Is it still installed by default if I'm running Xfce?
s/installed by default /installed by default under GNOME/
sixpack13 is old, sometimes blind and a lot more in this range.
He could NOT have everything everywhere on his/hims (?) radar, and and
On 10/15/19 19:48, George N. White III wrote:
You can test the claim: "Industry leading support: 2-year and free
24/7 technical
support. Contact ussupport@tp-link if you have any questions".
.
Yes, that sounds encouraging. Also I was pleased to see essential
information printed on the router
On Tue, 2019-10-15 at 19:06 -0700, ToddAndMargo via users wrote:
> How they get baobab out of "Gnome Disk Analyzer" is beyond me.
Whimsical names are Linux (and especially GNU) tradition. The baobab is
a tree with a complex root system, so it's appropriate in a way.
https://en.wikipedia.org/wiki/
On Tue, 2019-10-15 at 17:28 -0600, Joe Zeff wrote:
> On 10/15/2019 04:53 PM, Samuel Sieb wrote:
> > On 10/15/19 3:43 PM, Joe Zeff wrote:
> > > On 10/15/2019 03:05 PM, sixpack13 wrote:
> > > > installed by default and is under gnome programs => Utilities =>
> > > > "Disk Usage Analyse"
> > >
> >
I am running Fedora 30 (Cinnamon Spin) on a Dell XPS 13 (9380) laptop.
Until about early August, everything was working perfectly, but then,
with some update, suspend problems developed which I have difficulties
debugging.
Initially, I thought this is a kernel issue. Kernels up to
5.1.18-30
35 matches
Mail list logo
