additional information about my computer:
```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
$ uname -a
Linux joel-T470s 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020
x86_64
Public bug reported:
My computer hanged yesterday. After analysis, `/` is full, and all this
is due to `/var/log/syslog` and `/var/log/kern.log` being full of
messages from `tracker-extract`, until these logs get very large (3Go
each !), eventually preventing my computer to respond: I was even
Output of lspci | grep wireless -i
```
3a:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881214
Title:
syslog and
Output of `uname -a`:
Linux joel-T470s 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
I've got no idea how to reproduce the issue (happened yesterday evening,
only once), so I don't know if there would be an interest to boot on a
previous kernel
Hi all,
Same issue on my computer; `/var/log/syslog`, `/var/log/kern.log`, and
`journalctl` entries (`/var/log/journal//` folder) have grown
endlessly, until filling the partition, in less than an hour.
Xubuntu 20.04
Lenovo ThinkPad T470s
Following message is repeated again and again (around
I also have this bug with shotwell 0.22.0 on Ubuntu 15.04. That is quite
annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357279
Title:
Shotwell keeps writing metadata to files on every
Public bug reported:
# Context
Due to some problem I don't understand now, Shotwell crashes while updating
pictures metadata, resulting in empty or corrupted files.
[But that's not the point of this report. I may open a new ticket when I
understand the root cause.]
# What happens
it's that
Complementary information: if I remove the identified 0B-long picture,
shotwell goes further in starting but still crashes, only with the
already-quoted Glib-IO error. This was likely due to another picture
earlierly-corrupted by shotwell, that is attached here.
** Attachment added: "corrupted
(dunno how to edit previous comment) If I remove the attached picture,
shotwell still crashes during database loading.
AAAaah and of course, this happens when I have time to filter my
pictures :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
