Re: imminent /boot problem.

On 2/24/24 22:50, Tim via users wrote: Samuel Sieb (re: lost & found directory): That directory is also special. There might be consequences for recreating it. I don't know if it's accessed by name or inode. I would imagine there'd have to be reserved space in the partition so it doesn't

Re: tigervnc server configuration limitation

On 2/24/24 23:17, francis.montag...@inria.fr wrote: It does have something to do with running from systemd, but I have no idea what it is. Not sure at all of that. It seems to be instead an compatibility between vncsession and startxfce4. It's directly related to running from systemd while

Re: tigervnc server configuration limitation

On Sat, 24 Feb 2024 20:11:20 -0800 Samuel Sieb wrote: > On 2/24/24 08:52, Sam Varshavchik wrote: >> ... and that was because even xfce is not going to work. The reason was >> dumped into ~/.vnc/*log: >> /usr/bin/startxfce4: X server already running on display :1 >> MESA: error: ZINK: failed to

Re: imminent /boot problem.

Samuel Sieb (re: lost & found directory): > That directory is also special. There might be consequences for > recreating it. I don't know if it's accessed by name or inode. I would imagine there'd have to be reserved space in the partition so it doesn't otherwise fill up 100% making it

Re: imminent /boot problem.

Tim: >> I'm curious how you installed it in the first place, then? home user: > That was about 11 years ago, so my memory of that is foggy and > incomplete. > > I installed windows-7 first, probably from a CD purchased from a > local (near Washington, D.C) store. > > Then using either a CD

Re: imminent /boot problem.

On 2/24/24 7:10 PM, Tim via users wrote: On Sat, 2024-02-24 at 13:58 -0700, home user wrote: No other computer. No live boot. Tried making one multiple times with multiple sticks and multiple ports. Even a local youngish professional programmer (specializing in embedded and micro) could not

Re: tigervnc server configuration limitation

On 2/24/24 08:52, Sam Varshavchik wrote: ... and that was because even xfce is not going to work. The reason was dumped into ~/.vnc/*log: /usr/bin/startxfce4: X server already running on display :1 MESA: error: ZINK: failed to choose pdev glx: failed to create drisw screen failed to load

Re: imminent /boot problem.

On Sat, 2024-02-24 at 13:58 -0700, home user wrote: > No other computer. > No live boot. Tried making one multiple times with multiple sticks > and multiple ports. Even a local youngish professional programmer > (specializing in embedded and micro) could not figure it out. I'm curious how you

Re: tigervnc server configuration limitation

Samuel Sieb writes: On 2/24/24 08:52, Sam Varshavchik wrote: Sam Varshavchik writes: But something is still broken. I went through the motions, set session=xfce, but then something is still broken with systemd. systemctl start vncserver@: 1 results in: Feb 24 11:30:33

Re: tigervnc server configuration limitation

Samuel Sieb writes: On 2/24/24 07:10, Sam Varshavchik wrote: I'm not sure when Fedora switched to the current tigervnc systemd-based configuration, but: I've been using tigervnc to log in to an Ubuntu box, and it was simple to set up tigervnc on Ubuntu for remote access. I just tried the

Re: tigervnc server configuration limitation

On 2/24/24 08:52, Sam Varshavchik wrote: Sam Varshavchik writes: But something is still broken. I went through the motions, set session=xfce, but then something is still broken with systemd. systemctl start vncserver@:1 results in: Feb 24 11:30:33 monster.email-scan.com systemd[1]: Starting

Re: tigervnc server configuration limitation

On 2/24/24 07:10, Sam Varshavchik wrote: I'm not sure when Fedora switched to the current tigervnc systemd-based configuration, but: I've been using tigervnc to log in to an Ubuntu box, and it was simple to set up tigervnc on Ubuntu for remote access. I just tried the same on Fedora and was

Re: tigervnc server configuration limitation

On 24 Feb 2024 at 16:55, Sam Varshavchik wrote: From: Sam Varshavchik To: Community support for Fedora users Subject:Re: tigervnc server configuration limitation Date sent: Sat, 24 Feb 2024 16:55:05 -0500 Send reply to: Community support for Fedora users >

Re: tigervnc server configuration limitation

Michael D. Setzer II via users writes: As I stated. I've found Turbo VNC seems to work very well. At my home, I've got a notebook, and use it to vnc into 6 other Fedora 39 machines, and two windows machines in house. I hear you. I'm not married to tigervnc, just not sure if trying to get

Re: imminent /boot problem. [SOLVED (for a while!)]

On 2/22/24 11:21 AM, home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. Examine   Ignore -- Seeing

Re: imminent /boot problem.

On 2/24/24 1:34 PM, Samuel Sieb wrote: On 2/24/24 12:16, home user wrote: On 2/23/24 2:34 PM, Jon LaBadie wrote: On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>>

Re: imminent /boot problem.

you could delete it. it is create the next fsck run -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: imminent /boot problem.

On 2/23/24 3:31 PM, Felix Miata wrote: Samuel Sieb composed on 2024-02-23 16:48 (UTC-0500): home user wrote: -bash.4[~]: fdisk -l Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM006-2DM1 Units: sectors of 1 * 512 = 512 bytes Sector size

Re: imminent /boot problem.

On 2/23/24 2:51 PM, Samuel Sieb wrote: On 2/23/24 11:19, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> wrote: Is there anything in your /boot/lost+found? /boot/lost+found/: total 20 drwx--. 2

Re: imminent /boot problem.

On 2/23/24 2:48 PM, Samuel Sieb wrote: On 2/23/24 10:44, home user wrote: -bash.4[~]: fdisk -l Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM006-2DM1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size

Re: tigervnc server configuration limitation

As I stated. I've found Turbo VNC seems to work very well. At my home, I've got a notebook, and use it to vnc into 6 other Fedora 39 machines, and two windows machines in house. Also, vnc into remote machines in mom's house in Nevada. Windows machines all with the tigervnc since Turbo is link

Re: imminent /boot problem.

On 2/24/24 12:16, home user wrote: On 2/23/24 2:34 PM, Jon LaBadie wrote: On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user > wrote: Is there anything in your

Re: imminent /boot problem.

On 2/23/24 2:34 PM, Jon LaBadie wrote: On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> wrote: Is there anything in your /boot/lost+found? /boot/lost+found/:

Re: tigervnc server configuration limitation

francis.montag...@inria.fr writes: Hi. On Sat, 24 Feb 2024 11:52:40 -0500 Sam Varshavchik wrote: > But something is still broken. I went through the motions, set session=xfce, > ... and that was because even xfce is not going to work. The reason was > dumped into ~/.vnc/*log: >

Re: tigervnc server configuration limitation

Hi. On Sat, 24 Feb 2024 11:52:40 -0500 Sam Varshavchik wrote: > But something is still broken. I went through the motions, set session=xfce, > ... and that was because even xfce is not going to work. The reason was > dumped into ~/.vnc/*log: > /usr/bin/startxfce4: X server already running

Re: tigervnc server configuration limitation

Sam Varshavchik writes: Michael D. Setzer II via users writes: On 24 Feb 2024 at 10:10, Sam Varshavchik wrote: > That's a no-go for me. My Fedora system is configured to automatically log > into a graphical desktop. This won't work for me, then. Not sure on the latest version of tigervnc on

Re: tigervnc server configuration limitation

Michael D. Setzer II via users writes: On 24 Feb 2024 at 10:10, Sam Varshavchik wrote: > That's a no-go for me. My Fedora system is configured to automatically log > into a graphical desktop. This won't work for me, then. Not sure on the latest version of tigervnc on Fedora, for a while I was

Re: tigervnc server configuration limitation

On 24 Feb 2024 at 10:10, Sam Varshavchik wrote: From: Sam Varshavchik To: Fedora Users List Subject:tigervnc server configuration limitation Date sent: Sat, 24 Feb 2024 10:10:42 -0500 Send reply to: Community support for Fedora users > I'm not sure when Fedora switched to

tigervnc server configuration limitation

I'm not sure when Fedora switched to the current tigervnc systemd-based configuration, but: I've been using tigervnc to log in to an Ubuntu box, and it was simple to set up tigervnc on Ubuntu for remote access. I just tried the same on Fedora and was informed that launching vncserver was

TIP: X11's four clipboards

Hi All, A nice video on X11 four clipboards (Windows users do not know what they are missing): http://www.cs.man.ac.uk/~lindsec/secondary-selection.html I have no idea if all four work in Wayland (spelling). -T -- ___ users mailing list --