DeltaWingDragon

joined 1 year ago
[–] [email protected] 1 points 1 day ago (1 children)

I have flatseal installed. Did you read the post?

 

cross-posted from: https://sh.itjust.works/post/35352374

If I open a text file that needs root privileges to modify, I get this error:

Failed to save 'this_file': Insufficient permissions. Select 'Retry as Sudo' to retry as superuser.

That's fine, that's expected.

But when I click on "Retry as Sudo", I get this error:

Failed to save 'this_file': Unable to find pkexec or kdesudo.

This happens though pkexec is installed on my machine, at /usr/bin/pkexec; and I granted VSCodium access to it through Flatseal. How do I fix this?

[–] [email protected] 1 points 2 days ago (1 children)

Running as root is a forceful workaround, not the solution to my problem. I want to open this lock, not break it.

I don't want to run as root because...

  • It's bad for security. Think of running sudoedit vs sudo nano or sudo vim. If you run the editor as root directly, you can access the shell as root. This is a feature, not a bug! But if you run sudoedit, it stays at low privilege level until it actually saves the file.
  • The "Retry as Sudo" feature exists. If it's there, why not use it instead of circumventing it?
  • At this point, editing the file is irrelevant. This is not an XY problem. I want to stop getting the second error.

The "Retry as Sudo" dialog is supposed to appear, and when I click on the button, I am supposed to get a password prompt. That's what happens in the Apt version; that's what happens in the Snap version; and in the NixPKG version, they had the same problem, but they fixed it.

How do I fix it in my flatpak version?

[–] [email protected] 4 points 3 days ago (3 children)

sude

minor typo spotted

 

If I open a text file that needs root privileges to modify, I get this error:

Failed to save 'this_file': Insufficient permissions. Select 'Retry as Sudo' to retry as superuser.

That's fine, that's expected.

But when I click on "Retry as Sudo", I get this error:

Failed to save 'this_file': Unable to find pkexec or kdesudo.

This happens though pkexec is installed on my machine, at /usr/bin/pkexec; and I granted VSCodium access to it through Flatseal. How do I fix this?

[–] [email protected] 2 points 3 days ago* (last edited 3 days ago)

It could be a race condition: Check how long it takes between printing/typing each piece of text. Then try changing the length of the sleep statements, or removing them.

It could be overlapping text: Add a \n in each of your strings.

It could be some weird variable reuse issue: Print/type the strings directly, or use uniquely named variables (text1, text2, text3).

 

For example, if whenever I step from a standstill, I always use my right leg. Will my legs become asymmetrical?

396
Freud rule (sh.itjust.works)
 
[–] [email protected] 5 points 1 week ago

I found the simple life ain't so simple!

When I jumped out on that road

I got no love, no love you'd call real

Ain't got nobody waitin' at home!

Aah, yeah!

Running with the daemon!

[–] [email protected] 4 points 1 week ago

Gub-Gubs go Wooo!

[–] [email protected] 10 points 1 week ago (1 children)

A) What are you smoking

B) Where can I get some

[–] [email protected] 12 points 1 week ago (5 children)

Why is your font all wiggly?

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

A) It has the texture of plastic, and it is tasteless

B) I have eaten american "cheese"

[–] [email protected] 3 points 1 week ago

This should be a video, or a TV show, or something

 
 1. [✓] net.minetest.Minetest.Locale                    stable                i             flathub              5.8 kB / 1.6 MB   **
 2. [✓] org.freedesktop.Platform.GL.default             24.08                 i             flathub            156.2 MB / 156.6 MB
 3. [✓] org.freedesktop.Platform.GL.default             24.08extra            i             flathub             25.2 MB / 156.6 MB *
 4. [✓] org.freedesktop.Platform.Locale                 24.08                 i             flathub             18.6 kB / 380.3 MB **

Look at the asterisks. It downloads far less than what it says, yet it still completes and runs fine. How‽

 

Supposedly that is the path to my Firefox profile directory. But when I click "Open Directory", nothing happens.

When I access that file path, the directory (k45qdkms.default-release) does not exist.

 

cross-posted from: https://sh.itjust.works/post/32235573

I just installed a Debian 13 Trixie system on my laptop. I have 5 GPT partitions on 1 terabyte SSD and NO LVM!

partition layout

sda1 vfat 256M   EFI system partition
sda2 ext4 512M   boot partition
sda3 LUKS 460G   encrypted root
--   sda3_crypt  root partition, unlocks with passphrase
sda4 LUKS 465G   encrypted home
--   sda4_crypt  home partition, unlocks with passphrase
sda5 LUKS 4G     encrypted swap
--   sda5_crypt  swap partition, unlocks with keyfile

GRUB works fine, it loads the kernel, then I enter the password to decrypt my root partition. It decrypts correctly, then hangs for 1 minute 30 seconds.

After that, I get this error:

[ TIME ] Timed out waiting for device dev-mapper-sda4_crypt.device - /dev/mapper/sda4_crypt.
[DEPEND] Dependency failed for home.mount - /home/
[DEPEND] Dependency failed for local-fs.target - Local File Systems.
[DEPEND] Dependency failed for systemd-fsck@dev-mapper-sda4_crypt.service - File System Check on /dev/mapper/sda4_crypt.
[ TIME ] Timed out waiting for device dev-mapper-sda5_crypt.device - /dev/mapper/sda5_crypt.
[DEPEND] Dependency failed for dev-mapper-sda5_crypt.swap - /dev/mapper/sda5_crypt.
[DEPEND] Dependency failed for swap.target - Swaps

Not once does it ask me for the password to decrypt my home partition, it just waits until it fails.

 

I just installed a Debian 13 Trixie system on my laptop. I have 5 GPT partitions on 1 terabyte SSD and NO LVM!

partition layout

sda1 vfat 256M   EFI system partition
sda2 ext4 512M   boot partition
sda3 LUKS 460G   encrypted root
--   sda3_crypt  root partition, unlocks with passphrase
sda4 LUKS 465G   encrypted home
--   sda4_crypt  home partition, unlocks with passphrase
sda5 LUKS 4G     encrypted swap
--   sda5_crypt  swap partition, unlocks with keyfile

GRUB works fine, it loads the kernel, then I enter the password to decrypt my root partition. It decrypts correctly, then hangs for 1 minute 30 seconds.

After that, I get this error:

[ TIME ] Timed out waiting for device dev-mapper-sda4_crypt.device - /dev/mapper/sda4_crypt.
[DEPEND] Dependency failed for home.mount - /home/
[DEPEND] Dependency failed for local-fs.target - Local File Systems.
[DEPEND] Dependency failed for systemd-fsck@dev-mapper-sda4_crypt.service - File System Check on /dev/mapper/sda4_crypt.
[ TIME ] Timed out waiting for device dev-mapper-sda5_crypt.device - /dev/mapper/sda5_crypt.
[DEPEND] Dependency failed for dev-mapper-sda5_crypt.swap - /dev/mapper/sda5_crypt.
[DEPEND] Dependency failed for swap.target - Swaps

Not once does it ask me for the password to decrypt my home partition, it just waits until it fails.

 

cross-posted from: https://sh.itjust.works/post/31907670

When I use the Timeshift GUI to create a snapshot, it takes a very long time to complete. If I click Cancel, my desktop environment crashes and I get kicked to a black screen or a login prompt.

When I use Timeshift CLI, it creates the snapshot in less than a second, but the command waits for a long time afterward. However, it can be safely interrupted with control-C.

Timeshift is in BTRFS mode.

Output of Timeshift command, interrupted

Using system disk as snapshot device for creating snapshots in BTRFS mode
Mounted '/dev/dm-0 (sda3)' at '/run/timeshift/33685/backup'
btrfs: Quotas are not enabled
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/33685/backup
Created directory: /run/timeshift/33685/backup/timeshift-btrfs/snapshots/2025-01-29_15-21-49
Created subvolume snapshot: /run/timeshift/33685/backup/timeshift-btrfs/snapshots/2025-01-29_15-21-49/@
Created control file: /run/timeshift/33685/backup/timeshift-btrfs/snapshots/2025-01-29_15-21-49/info.json
BTRFS Snapshot saved successfully (0s)
^C

#output of time command
real    0m1.165s
user    0m0.004s
sys     0m0.009s

Output of Timeshift command, run to completion

[Warning] Deleted invalid lock
Using system disk as snapshot device for creating snapshots in BTRFS mode
Mounted '/dev/dm-0 (sda3)' at '/run/timeshift/32947/backup'
btrfs: Quotas are not enabled
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/32947/backup
Created directory: /run/timeshift/32947/backup/timeshift-btrfs/snapshots/2025-01-29_15-13-13
Created subvolume snapshot: /run/timeshift/32947/backup/timeshift-btrfs/snapshots/2025-01-29_15-13-13/@
Created control file: /run/timeshift/32947/backup/timeshift-btrfs/snapshots/2025-01-29_15-13-13/info.json
BTRFS Snapshot saved successfully (0s)
Tagged snapshot '2025-01-29_15-13-13': ondemand
------------------------------------------------------------------------------
Maximum backups exceeded for backup level 'weekly'

#output of time command
real    1m12.419s
user    0m0.001s
sys     0m0.009s

Possibly related to this bug?

 

When I use the Timeshift GUI to create a snapshot, it takes a very long time to complete. If I click Cancel, my desktop environment crashes and I get kicked to a black screen or a login prompt.

When I use Timeshift CLI, it creates the snapshot in less than a second, but the command waits for a long time afterward. However, it can be safely interrupted with control-C.

Timeshift is in BTRFS mode.

Output of Timeshift command, interrupted

Using system disk as snapshot device for creating snapshots in BTRFS mode
Mounted '/dev/dm-0 (sda3)' at '/run/timeshift/33685/backup'
btrfs: Quotas are not enabled
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/33685/backup
Created directory: /run/timeshift/33685/backup/timeshift-btrfs/snapshots/2025-01-29_15-21-49
Created subvolume snapshot: /run/timeshift/33685/backup/timeshift-btrfs/snapshots/2025-01-29_15-21-49/@
Created control file: /run/timeshift/33685/backup/timeshift-btrfs/snapshots/2025-01-29_15-21-49/info.json
BTRFS Snapshot saved successfully (0s)
^C

#output of time command
real    0m1.165s
user    0m0.004s
sys     0m0.009s

Output of Timeshift command, run to completion

[Warning] Deleted invalid lock
Using system disk as snapshot device for creating snapshots in BTRFS mode
Mounted '/dev/dm-0 (sda3)' at '/run/timeshift/32947/backup'
btrfs: Quotas are not enabled
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/32947/backup
Created directory: /run/timeshift/32947/backup/timeshift-btrfs/snapshots/2025-01-29_15-13-13
Created subvolume snapshot: /run/timeshift/32947/backup/timeshift-btrfs/snapshots/2025-01-29_15-13-13/@
Created control file: /run/timeshift/32947/backup/timeshift-btrfs/snapshots/2025-01-29_15-13-13/info.json
BTRFS Snapshot saved successfully (0s)
Tagged snapshot '2025-01-29_15-13-13': ondemand
------------------------------------------------------------------------------
Maximum backups exceeded for backup level 'weekly'

#output of time command
real    1m12.419s
user    0m0.001s
sys     0m0.009s

Possibly related to this bug?

 

Hello?

1
Fox rule (sh.itjust.works)
 
view more: next ›