I did look across the internet and from what I gathered is that the XSession and X11 window system use this file to redirect all the standard error (stderr) messages/logs to this file. Also it is mentioned that the configuration of .xsession-errors is controlled by the file /etc/X11/Xsession. When I looked inside Xsession this is the comment that was mentionedWas not able to confirm if the Wayland and KDE also use .xsession-errors or not. Also did not find any information on using logrotate to control this file's growth. If you have any pointers can you please share them?
I did not look for linking this file to some other file say in /var/log directory or some other directory. The Xsession file did have a failsafe in which it would try to create a file in the /tmp directory. But that did not work.
I had a look inside the file .xsession-errors to figure out what was reporting inside it, but was unable to make sense of it. First of all there is not timestamp given for any of these log entries inside the file. Secondly there is no calling program name, i.e. the name of the program that is causing the issue. For example look at a sample extract from the old .xsession-errors file given below. I could not determine when this occurred and what program is causing this.
And this I confirmed. If I delete the file then yes X, SDDM, KDE do not start. I had to go and give the following commands to get X11 to work# attempt to create an error file; abort if we cannot
Code:
$ touch $HOME/.xsession-errors$ chmod 600 $HOME/.xsession-errorsI did not look for linking this file to some other file say in /var/log directory or some other directory. The Xsession file did have a failsafe in which it would try to create a file in the /tmp directory. But that did not work.
I had a look inside the file .xsession-errors to figure out what was reporting inside it, but was unable to make sense of it. First of all there is not timestamp given for any of these log entries inside the file. Secondly there is no calling program name, i.e. the name of the program that is causing the issue. For example look at a sample extract from the old .xsession-errors file given below. I could not determine when this occurred and what program is causing this.
Code:
kf.itemviews: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets!kf.itemviews: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets!kf.itemviews: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets!kf.itemviews: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets!QObject::disconnect: Unexpected nullptr parameterQObject::disconnect: Unexpected nullptr parameterkf.coreaddons: Expected a KPluginFactory, got a KIOPluginForMetaData............QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*The X11 connection broke: I/O error (code 1)XIO: fatal IO error 4 (Interrupted system call) on X server ":0" after 780 requests (780 known processed) with 0 events remaining.kf.notifications: Had queued notifications on destruction. Was the eventloop running?M 11:54:46.129123 wireplumber ../src/main.c:372:signal_handler: stopped by signal: TerminatedAsked to handle disabled watch: 0x5633d3bb4000 31Asked to handle disabled watch: 0x5633d3ba2960 26M 11:54:46.148663 wireplumber ../src/main.c:364:on_disconnected: disconnected from pipewireStatistics: Posted by LinuxSpring1 — Wed Aug 14, 2024 1:13 am