Bug 4663 - Status messages in $HOME/.xsession-errors
Summary: Status messages in $HOME/.xsession-errors
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.17.5
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2023-02-17 13:52 UTC by andrew.woodward
Modified: 2023-02-17 14:05 UTC (History)
0 users

See Also:


Attachments

Description andrew.woodward 2023-02-17 13:52:31 UTC
inxi -Fxxxrz
System:
  Kernel: 5.4.0-139-generic arch: x86_64 bits: 64 compiler: gcc v: 9.4.0
    Desktop: MATE v: 1.26.0 info: mate-panel wm: marco v: 1.26.0 vt: 7
    dm: LightDM v: 1.30.0 Distro: Linux Mint 20.3 Una
    base: Ubuntu 20.04 focal
Machine:
  Type: Desktop Mobo: FOXCONN model: A6GMV v: 0A serial: <superuser required>
    BIOS: American Megatrends v: 080014 date: 07/22/2010
CPU:
  Info: quad core model: AMD Athlon II X4 640 bits: 64 type: MCP
    smt: <unsupported> arch: K10 rev: 3 cache: L1: 512 KiB L2: 2 MiB
  Speed (MHz): avg: 1050 high: 1800 min/max: 800/3000 boost: disabled
    cores: 1: 1800 2: 800 3: 800 4: 800 bogomips: 24000
  Flags: ht lm nx pae sse sse2 sse3 sse4a svm
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 430] driver: nvidia v: 390.157 pcie:
    speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:0de1 class-ID: 0300
  Display: x11 server: X.Org v: 1.20.13 with: Xwayland compositor: marco
    v: 1.26.0 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.87x11.85")
    s-diag: 610mm (24")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 93
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
  OpenGL: renderer: GeForce GT 430/PCIe/SSE2 v: 4.6.0 NVIDIA 390.157
    direct render: Yes



Every time claws-mail retrieves mail it writes status (NOT error) messages to $HOME/.xsession-errors

Brief sample below:

=====
** Message: 11:42:05.742: Account '**********': Connecting to POP3 server: **********:110...

** Message: 11:42:06.157: Account '**********': Connecting to POP3 server: **********:110...

** Message: 11:42:06.597: Account '**********': Connecting to POP3 server: **********:110...

** Message: 11:42:07.269: rule is not account-based

** Message: 11:42:07.269: message does not match

** Message: 11:42:07.269: disabled rule 'Ageas' [ from matchcase "noreply@myageas.co.uk" mark_as_read delete stop ]

** Message: 11:42:07.269: rule is not account-based

** Message: 11:42:07.269: message does not match

** Message: 11:42:07.269: rule is not account-based

** Message: 11:42:07.269: message does not match

** Message: 11:42:07.269: rule is not account-based
:
etc
=====

My current .xsession-errors has accumulated 174614 such messages in 8 days.

Should these messages not be written to a separate log file (and probably over-written each time mail is fetched)?
Comment 1 Paul 2023-02-17 14:05:18 UTC
It's not Claws Mail which is causing g_warning messages to be put in .xsession-errors, this is some configuration outside of Claws Mail.

Note You need to log in before you can comment on or make changes to this bug.