LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-23-2024, 04:30 PM   #4006
gian_d
Member
 
Registered: Nov 2019
Location: Cagliari, Sardinia (Italy)
Distribution: Slackware
Posts: 76

Rep: Reputation: Disabled

Quote:
Originally Posted by gian_d View Post
Hi, I don't know if this happens only in my system, but after last updates, GIMP crashes due a segmentation fault when quitting the application. It works fine, the crash happens only closing the program.

It is possible that a rebuild is needed to solve it, I'll try to rebuild from sources tomorrow.
No, the error still occurs even after the recompilation
 
Old 03-23-2024, 05:04 PM   #4007
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,812

Rep: Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487
Quote:
Originally Posted by gian_d View Post
Hi, I don't know if this happens only in my system, but after last updates, GIMP crashes due a segmentation fault when quitting the application.
It stopped crashing after downgrading to these:
Code:
glib2-2.78.4-x86_64-1
at-spi2-core-2.50.1-x86_64-1
gvfs-1.52.2-x86_64-2
ibus-1.5.29-x86_64-1
 
Old 03-23-2024, 05:13 PM   #4008
bigbadaboum
Member
 
Registered: Apr 2023
Posts: 145

Rep: Reputation: 58
Quote:
glennmcc
Member
Unlikely, but...

If I recall correctly, even the 32bit Linux kernels fixed the 2038 date problem a long time ago.

----

Yep, fixed.

https://www.gnu.org/software/gnulib/...8-problem.html
I just changed the time in the bios 23-03-2040, I stay offline, I reboot Slackware64 2 times.

"date" give a good answer.
But at the boot I have the message "last login: tue 'feb 16 16:30:07 +009 1904 on dev/tty1."

There is still 32-bit ???
 
2 members found this post helpful.
Old 03-23-2024, 05:22 PM   #4009
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 146

Rep: Reputation: 237Reputation: 237Reputation: 237
Quote:
Originally Posted by gian_d View Post
Hi, I don't know if this happens only in my system, but after last updates, GIMP crashes due a segmentation fault when quitting the application. It works fine, the crash happens only closing the program.
It's crashing here, too, but only when I have unsaved changes, select "Close All" or "Quit" and then confirm with "Discard Changes" → crash. Closing unsaved files one by one works. I also tried a recompiled GIMP but without success.

My latest update is from Wed Mar 20 21:10:30 UTC 2024.
 
2 members found this post helpful.
Old 03-23-2024, 05:51 PM   #4010
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,386

Rep: Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105
Quote:
Originally Posted by Markus Wiesner View Post
It's crashing here, too, but only when I have unsaved changes, select "Close All" or "Quit" and then confirm with "Discard Changes" → crash. Closing unsaved files one by one works. I also tried a recompiled GIMP but without success.

My latest update is from Wed Mar 20 21:10:30 UTC 2024.
It has been reported here:
https://gitlab.gnome.org/GNOME/gimp/-/issues/11019

EDIT:
Thank you Petri for the crash dump

Last edited by marav; 03-24-2024 at 08:21 AM.
 
2 members found this post helpful.
Old 03-23-2024, 09:41 PM   #4011
glennmcc
Member
 
Registered: Jan 2021
Location: North Jackson, Ohio (USA)
Distribution: slackware64-15.0
Posts: 525

Rep: Reputation: 298Reputation: 298Reputation: 298
Quote:
Originally Posted by bigbadaboum View Post
I just changed the time in the bios 23-03-2040, I stay offline, I reboot Slackware64 2 times.

"date" give a good answer.
But at the boot I have the message "last login: tue 'feb 16 16:30:07 +009 1904 on dev/tty1."

There is still 32-bit ???
Which kernel version are you running ?
 
Old 03-24-2024, 02:52 AM   #4012
gian_d
Member
 
Registered: Nov 2019
Location: Cagliari, Sardinia (Italy)
Distribution: Slackware
Posts: 76

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
Well, we have to wait a fix
 
Old 03-24-2024, 02:55 AM   #4013
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 1,812

Rep: Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487Reputation: 1487
Quote:
Originally Posted by Petri Kaukasoina View Post
It stopped crashing after downgrading to these:
Code:
glib2-2.78.4-x86_64-1
...
We got a new glib:
Code:
using GLib version 2.80.0 (compiled against version 2.78.2)
Quote:
Originally Posted by marav View Post
A new glib there, too:
Code:
using GLib version 2.79.1 (compiled against version 2.78.1)
 
Old 03-24-2024, 02:58 AM   #4014
mistfire
Member
 
Registered: Jun 2021
Posts: 40

Rep: Reputation: Disabled
duktape on gjs

Using duktape on polkit was great. I wonder if gjs can be compiled on duktape instead of mozjs for smaller dependencies?
 
Old 03-24-2024, 05:40 AM   #4015
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,386

Rep: Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105Reputation: 4105
Quote:
Originally Posted by mistfire View Post
Using duktape on polkit was great. I wonder if gjs can be compiled on duktape instead of mozjs for smaller dependencies?
Code:
GJS is a JavaScript runtime built on Firefox's SpiderMonkey 
JavaScript engine and the GNOME platform libraries.
https://gitlab.gnome.org/GNOME/gjs

Last edited by marav; 03-24-2024 at 08:21 AM.
 
Old 03-24-2024, 06:37 AM   #4016
henca
Member
 
Registered: Aug 2007
Location: Linköping, Sweden
Distribution: Slackware
Posts: 977

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665
Quote:
Originally Posted by bigbadaboum View Post
I just changed the time in the bios 23-03-2040, I stay offline, I reboot Slackware64 2 times.

"date" give a good answer.
But at the boot I have the message "last login: tue 'feb 16 16:30:07 +009 1904 on dev/tty1."

There is still 32-bit ???
My guess is that you get that message at login rather than boot. I would also guess that time is taken from the wtmp functionality and not the kernel. According to the man page of wtmp it does indeed have 32 bit time entries on x68_64:

Code:
               /* The ut_session and ut_tv fields must be the same size when
                  compiled 32- and 64-bit.  This allows data files and shared
                  memory to be shared between 32- and 64-bit applications. */
           #if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32
               int32_t ut_session;           /* Session ID (getsid(2)),
                                                used for windowing */
               struct {
                   int32_t tv_sec;           /* Seconds */
                   int32_t tv_usec;          /* Microseconds */
               } ut_tv;                      /* Time entry was made */
           #else
                long   ut_session;           /* Session ID */
                struct timeval ut_tv;        /* Time entry was made */
           #endif
Code:
       Note  that  on  biarch  platforms,  that is, systems which can run both
       32-bit and 64-bit applications (x86-64, ppc64, s390x, etc.),  ut_tv  is
       the  same  size  in  32-bit  mode as in 64-bit mode.  The same goes for
       ut_session and ut_time if they are present.  This allows data files and
       shared  memory  to  be  shared  between 32-bit and 64-bit applications.
       This is achieved by changing the type of  ut_session  to  int32_t,  and
       that  of  ut_tv to a struct with two int32_t fields tv_sec and tv_usec.
       Since ut_tv may not be the same as struct timeval, then instead of  the
       call:

           gettimeofday((struct timeval *) &ut.ut_tv, NULL);

       the following method of setting this field is recommended:

           struct utmp ut;
           struct timeval tv;

           gettimeofday(&tv, NULL);
           ut.ut_tv.tv_sec = tv.tv_sec;
           ut.ut_tv.tv_usec = tv.tv_usec;
regards Henrik
 
2 members found this post helpful.
Old 03-24-2024, 08:39 AM   #4017
bigbadaboum
Member
 
Registered: Apr 2023
Posts: 145

Rep: Reputation: 58
Quote:
glennmcc
Member
Which kernel version are you running ?
https://www.gnu.org/software/gnulib/...8-problem.html
Quote:
With the ‘year2038-recommended’ module, configure by default should work on the following 32-bit platforms (or 32-bit ABIs in bi-arch systems):

Linux kernel 5.1 (2019) and later with glibc 2.34 (2021) and later on x86, arm, mips (o32 or n32 ABI), powerpc32, sparc32, s390, hppa, m68k, sh, csky, microblaze, nios2,
I run on franken-Slackware64 not 32-bit but I restart the test with a 5.4 kernel, I always have the same message "last login 1904".

*Henca wrote her message while I was writing mine.
mystery resolved thank you very much Henca.

Last edited by bigbadaboum; 03-24-2024 at 08:48 AM.
 
1 members found this post helpful.
Old 03-24-2024, 12:19 PM   #4018
glennmcc
Member
 
Registered: Jan 2021
Location: North Jackson, Ohio (USA)
Distribution: slackware64-15.0
Posts: 525

Rep: Reputation: 298Reputation: 298Reputation: 298
Quote:
Originally Posted by henca View Post
My guess is that you get that message at login rather than boot. I would also guess that time is taken from the wtmp functionality and not the kernel. According to the man page of wtmp it does indeed have 32 bit time entries on x68_64:
regards Henrik
Well then, it looks like a '2038 fix' is needed for wtmp
 
Old 03-24-2024, 12:38 PM   #4019
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,901

Rep: Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025Reputation: 5025
Quote:
Originally Posted by glennmcc View Post
Well then, it looks like a '2038 fix' is needed for wtmp
By the sounds of this it seems they intend to just leave it to rot.
 
1 members found this post helpful.
Old 03-24-2024, 01:31 PM   #4020
glennmcc
Member
 
Registered: Jan 2021
Location: North Jackson, Ohio (USA)
Distribution: slackware64-15.0
Posts: 525

Rep: Reputation: 298Reputation: 298Reputation: 298
Quote:
Originally Posted by GazL View Post
By the sounds of this it seems they intend to just leave it to rot.
Yes, that page a couple of others seem to suggest that the 'fix' will be to switch from sysvinit to systemd

Time will tell whether or not Patrick decides to make that switch sometime in the future.

Time will also tell whether or not he decides to drop 32bit all-together and have only 64bit Slackware.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Apache 2.4 requests to non-SSL site with "Upgrade-Insecure-Requests: 1" and no trailing / get redirected to default site owendelong Linux - Server 2 06-22-2021 02:08 PM
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:57 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration