On 5/21/23 20:02, home user wrote:
I notice that the themes/starfield subdirectory has quite a few (31)
files, all from July 06, 2017, a few quite big. But should not assume
that being old means they're no longer needed.
My question: Is anything in this directory still needed. I'd like to
On 5/21/23 20:02, home user wrote:
On 5/18/23 4:21 PM, home user wrote:
[... snip ...]
There are two more /boot subdirectories I want to look at:
/boot/grub2/i386-pc/
/boot/grub2/themes/starfield/
I did an "ls -lRt" on /boot/grub2/ and put the output (as a text file)
onto the google drive
On 5/18/23 4:21 PM, home user wrote:
[... snip ...]
There are two more /boot subdirectories I want to look at:
/boot/grub2/i386-pc/
/boot/grub2/themes/starfield/
I did an "ls -lRt" on /boot/grub2/ and put the output (as a text file) onto the
google drive here:
On May 21, 2023, at 20:57, Robert Nichols wrote:
>
> Not quite. What happens is that your shell's exec() call fails with "ENOEXEC
> (Exec format error)". When your shell (not the kernel) sees that for a file
> that does have execute permission, it forks a copy of itself to try to
> interpret
On 5/21/23 08:47, Jonathan Billings wrote:
On May 20, 2023, at 22:18, Michael D. Setzer II wrote:
Recently was getting a strange error when running a script that didn't have
#!/usr/bin/bash at top?
free(): invalid next size (fast)
Aborted (core dumped)
Just adding the line fixes the issue,
On Mon, 2023-05-22 at 08:55 +1000, Michael D. Setzer II via users
wrote:
> start1.sh
> #!/usr/bin/bash
> echo Start
>
> or
> start2.sh
> echo Start
>
> Have filed a bug report with xfce-terminal.
But does it work consistently, everywhere, when you have a shebang at
the start of the script?
On 21 May 2023 at 16:52, Roger Heflin wrote:
From: Roger Heflin
Date sent: Sun, 21 May 2023 16:52:56 -0500
Subject:Re: Strange error running scripts. without
#!/usr/bin/bash
To: Community support for Fedora users
Send reply
That usually implies something in the profile/bashrc and such is
hitting the bug under some condition.
On Sun, May 21, 2023 at 5:14 PM Michael D. Setzer II via users
wrote:
>
> On 21 May 2023 at 16:52, Roger Heflin wrote:
>
> From: Roger Heflin
> Date sent: Sun,
On 21 May 2023 at 16:52, Roger Heflin wrote:
From: Roger Heflin
Date sent: Sun, 21 May 2023 16:52:56 -0500
Subject:Re: Strange error running scripts. without
#!/usr/bin/bash
To: Community support for Fedora users
Send reply
You should be able to add -f (follow all forks) on strace and it will
follow everything. But without the script tracing POC mentions you
aren't really going to know what line gets the error.
It is likely the bug is in one of the commands you are using, and it
may depend on the data you are
On Mon, 2023-05-22 at 07:09 +1000, Michael D. Setzer II via users
wrote:
> Located the earlier script. It still gave the error so tried
> strace and got
> strace ./mktext2x.sh
> execve("./mktext2x.sh", ["./mktext2x.sh"],
> 0x7ffc37e55570 /* 35 vars */) = -1 ENOEXEC (Exec
> format error)
>
On 5/21/23 14:09, Michael D. Setzer II via users wrote:
On 21 May 2023 at 16:05, Go Canes wrote:
From: Go Canes
Date sent: Sun, 21 May 2023 16:05:06 -0400
Subject:Re: Strange error running scripts. without
#!/usr/bin/bash
To:
On 21 May 2023 at 16:05, Go Canes wrote:
From: Go Canes
Date sent: Sun, 21 May 2023 16:05:06 -0400
Subject:Re: Strange error running scripts. without
#!/usr/bin/bash
To: mi...@guam.net,
Community support for Fedora
On Sun, May 21, 2023 at 3:29 PM Michael D. Setzer II via users
wrote:
>
> On 21 May 2023 at 16:05, Go Canes wrote:
>
> From: Go Canes
> Date sent: Sun, 21 May 2023 16:05:06 -0400
> Subject:Re: Strange error running scripts. without
> #!/usr/bin/bash
On 21 May 2023 at 16:05, Go Canes wrote:
From: Go Canes
Date sent: Sun, 21 May 2023 16:05:06 -0400
Subject:Re: Strange error running scripts. without
#!/usr/bin/bash
To: mi...@guam.net,
Community support for Fedora
On Sat, May 20, 2023 at 10:18 PM Michael D. Setzer II
wrote:
> Recently was getting a strange error when running a script that didn't have
> #!/usr/bin/bash at top?
> free(): invalid next size (fast)
> Aborted (core dumped)
> Just adding the line fixes the issue, but not sure why??
> Have run
On 21/05/2023 18:05, stan via users wrote:
1. Caveat: This is a complex procedure, and from your past posts of
your skill level, maybe too risky for you to do.
There is lots of room in / for /boot. Right now you are using a
separate /boot, but there is a way to use a /boot under the
root
Robert McBroom via users wrote:
> ~]# route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> default _gateway 0.0.0.0 UG 100 0 0 eno1
> 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0
I don't care about your story so i am here for the IT
Dorian Rosse.
From: John Pilkington
Sent: Thursday, May 18, 2023 10:40:08 PM
To: users@lists.fedoraproject.org
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an
On 5/21/23 01:08, Tim via users wrote:
On Sun, 2023-05-21 at 00:43 -0400, Robert McBroom via users wrote:
Recently the f37 system is unable to access the internet. It accesses
the local network. The web page for the isp router is there and it
accesses my NAS. Tried a USB WIFI adapter and get
Ignore this post if you are happy with the current resolution to your
issue.
On Sat, 20 May 2023 18:17:56 -0600
home user wrote:
> On 5/20/23 3:03 PM, Patrick O'Callaghan wrote:
> > On Sun, 2023-05-21 at 04:12 +0930, Tim via users wrote:
> >> On Sat, 2023-05-20 at 17:07 +0100, Patrick
On Sat, 20 May 2023 19:29:48 -0400
Ranbir wrote:
> Hello Everyone,
>
> I've successfully been using the Nextcloud plugin for GNOME's Online
> Accounts feature for a long time. Recently I upgraded to Fedora 37 and
> the Nextcloud integration stopped working because the authentication
> is
On May 21, 2023, at 09:47, Jonathan Billings wrote:
>
>
>>
>> On May 20, 2023, at 22:18, Michael D. Setzer II wrote:
>>
>>
>> Recently was getting a strange error when running a script that didn't have
>> #!/usr/bin/bash at top?
>> free(): invalid next size (fast)
>> Aborted (core
On May 20, 2023, at 22:18, Michael D. Setzer II wrote:
>
>
> Recently was getting a strange error when running a script that didn't have
> #!/usr/bin/bash at top?
> free(): invalid next size (fast)
> Aborted (core dumped)
> Just adding the line fixes the issue, but not sure why??
> Have run
24 matches
Mail list logo
