Re: Is it possible to convert a live image on a USB to a running system on that same USB

[Terry Polzin]

Barry,

I tried that, the installer only seems to consider devices it detects as
hard drives.

On Mon, Sep 5, 2022 at 5:57 PM Barry  wrote:

>
>
> On 4 Sep 2022, at 23:56, Terry Polzin  wrote:
>
> 
> To be clear, I don't want to install a disk device.
>
> Basically I need a procedure to
>
>
>- Remove the livecd user and disable auto login.
>- Keep grub intact on the USB and write it's updates there.
>
> I'm perfectly happy booting the USB via the BIOS.  I am currently testing
> with the XFCE-live image.
>
> Thanks for any pointers.
>
>
> No you cannot do it in place.
>
> But what you can do is install from the live image to a 2nd usb stick.
>
> Barry
>
>
>
>
>
>
>
>
>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: "Dummy output" instead of sound card options, was working, now gone.

[Dave Ulrick]

On 9/5/22 5:04 PM, Barry wrote:

I would expect that the hardware support is in the kernel.
I thought alsa-lib did not have hardware specific code.
Maybe try booting an older kernel to see the device comes back?


If booting into an older kernel doesn't help...

When hardware seems to disappear, I'd suggest doing a cold boot: shut 
down, wait for power off, and turn power back on. Every so often I see 
hardware go into a weird state that doesn't get reinitialized with a 
(warm) reboot but does with a cold boot.


Dave
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: "Dummy output" instead of sound card options, was working, now gone.

[Barry]

> On 5 Sep 2022, at 18:32, stan via users  wrote:
> 
> On Sun, 4 Sep 2022 14:44:11 -0400
> Ted Roche  wrote:
> 
>>> On Sun, Sep 4, 2022 at 1:19 AM stan via users
>>>  wrote:
>>> 
>>> On Sat, 3 Sep 2022 11:19:27 -0400
>>> Ted Roche  wrote:  
 
 Basic troubleshooting pointers on what to search for would be
 appreciated.  
>>> 
>>> aplay -l
>>> should show any devices that alsa recognizes.  If alsa doesn't
>>> recognize a device, you won't be able to use it.  If alsa knows
>>> about the device, I would then use pavucontrol to activate it by
>>> setting it as default.  
> 
>> aplay -l only seems to find HDMI devices:
> 
> I think that is your problem.  If alsa doesn't recognize the device,
> when it used to, then there is probably a hardware error.  To be sure,
> you should check when alsa-lib was installed,
> rpm -qi alsa-lib

I would expect that the hardware support is in the kernel.
I thought alsa-lib did not have hardware specific code.
Maybe try booting an older kernel to see the device comes back?

Barry


> If that was around the time your device stopped working, it could be a
> regression in the library.  They do happen, but it isn't common.  You
> can try a downgrade to an earlier alsa-lib by downloading the packages
> you have installed from here,
> https://koji.fedoraproject.org/koji/packageinfo?packageID=410
> and install them with
> dnf -C downgrade [list of binary rpms]
> in the directory to where you downloaded them.
> 
> If it is a discrete sound device, you could try reseating it, in case
> it is no longer making good contact.  Do you have another sound device
> you can install as a check?
> 
> If you run 
> journalctl -b0
> to look at the last boot, what does it show for sound device
> initialization?  Is there any kind of error when it tries to activate
> the device that is no longer working?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Is it possible to convert a live image on a USB to a running system on that same USB

[Barry]

> On 4 Sep 2022, at 23:56, Terry Polzin  wrote:
> 
> 
> To be clear, I don't want to install a disk device.
> 
> Basically I need a procedure to
> 
> Remove the livecd user and disable auto login.
> Keep grub intact on the USB and write it's updates there.
> I'm perfectly happy booting the USB via the BIOS.  I am currently testing 
> with the XFCE-live image.
> 
> Thanks for any pointers.

No you cannot do it in place.

But what you can do is install from the live image to a 2nd usb stick.

Barry

> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Duplex Printer Problem

[Jonathan Ryshpan]

On Tue, 2022-08-30 at 07:14 -0700, Jonathan Ryshpan wrote:
> Whenever I try to print from Okular, a box with this message appears:
>There are conflicts in duplex settings. Do you want to fix them?
> And printing is in fact funky: the options for double sided printing:
>Okular->Print->Options
> are strange. The option "Long Side Printing" is selected (though
> greyed out); the option "Off" is selectable, but if selected, no other
> option can be selected afterward. Firefox doesn't allow control of
> duplex printing using its native print dialog, but duplex can be
> controlled using the system dialog.
> 
> Does anyone know what's going on or how to fix it.
> 
> Printer:
>HP Color Laserjet M255dw
> 
> Cups Version:
>cups-2.4.2-4.fc36.x86_64
> 
> System Info:
>Operating System: Fedora Linux 36
>KDE Plasma Version: 5.25.4
>KDE Frameworks Version: 5.97.0
>Qt Version: 5.15.5
>Kernel Version: 5.19.4-200.fc36.x86_64 (64-bit)
>Graphics Platform: X11
>Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
>Memory: 15.5 GiB of RAM
>Graphics Processor: Mesa Intel® HD Graphics 4600

I tried running 
 $ hp-check --run
which appears to be largely undocumented, and which produced the
following errors. The list looks very strange. Does anyone know what's
going on? The entire output is attached as hp-check.log .
   
   ---
   | SUMMARY |
   ---
   
   Missing Required Dependencies
   -
   error: 'cups' package is missing or 'cups' service is not running.
   error: 'libjpeg-devel' package is missing/incompatible  
   error: 'cups-devel' package is missing/incompatible  
   error: 'cups-devel' package is missing/incompatible  
   error: 'libusb1-devel' package is missing/incompatible  
   error: 'sane-backends-devel' package is missing/incompatible  
   error: 'avahi-devel' package is missing/incompatible  
   error: 'net-snmp-devel' package is missing/incompatible  
   error: 'python3-devel' package is missing/incompatible  
   error: 'libtool' package is missing/incompatible  
   error: 'rpm-build' package is missing/incompatible  
   
   Missing Optional Dependencies
   -
   error: 'polkit' package is missing/incompatible  
   error: 'polkit-gnome' package is missing/incompatible  
   error: 'PKG_FROM_PIP:notify2' package is missing/incompatible  
   
   Total Errors: 12
   Total Warnings: 0
   

-- 
Sincerely Jonathan Ryshpan 

 The time you enjoy wasting is not wasted time.
 --Bertrand Russell
hp-check[44389]: info: :
hp-check[44389]: info: :[01mHP Linux Imaging and Printing System (ver. 3.22.6)[0m
hp-check[44389]: info: :[01mDependency/Version Check Utility ver. 15.1[0m
hp-check[44389]: info: :
hp-check[44389]: info: :Copyright (c) 2001-18 HP Development Company, LP
hp-check[44389]: info: :This software comes with ABSOLUTELY NO WARRANTY.
hp-check[44389]: info: :This is free software, and you are welcome to distribute it
hp-check[44389]: info: :under certain conditions. See COPYING file for more details.
hp-check[44389]: info: :
hp-check[44389]: info: :[01mNote: hp-check can be run in three modes:[0m
hp-check[44389]: info: :1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are  
hp-check[44389]: info: :installed to successfully compile HPLIP.   
hp-check[44389]: info: :2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper  
hp-check[44389]: info: :dependencies installed to successfully run.
hp-check[44389]: info: :3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). 
hp-check[44389]: info: :
hp-check[44389]: info: :Check types:   
hp-check[44389]: info: :a. EXTERNALDEP - External Dependencies 
hp-check[44389]: info: :b. GENERALDEP - General Dependencies (required both at compile and run time)   
hp-check[44389]: info: :c. COMPILEDEP - Compile time Dependencies  
hp-check[44389]: info: :d. [All are run-time chec

Re: fstab: systemd still uses the old version

[Tim via users]

On Mon, 2022-09-05 at 11:06 -0300, George N. White III wrote:
> For every person who reports a problem like this there are dozens if not 
> hundreds 
> who never report the problem.  Many will discover outdated or incorrect 
> advice from the internet.
> Some will decide that linux doesn't work and stick with Windows. 
> 
> There is a simple and effective solution, but it is buried under a mass of 
> internet garbage, for example:
> 
> itsfoss.com: wrong-time-dual-boot/ mentions "Make Windows use UTC time for 
> the hardware 
> clock" but the fix is not provided.

I think a large part of the inertia on doing much about this is, is
that other than at boot time the hardware clock is generally ignored,
giving a prevailing attitude that the program is fixed elsewhere.

Often it is, the clock will simply be set sometime during boot.  It
doesn't help you with log files, but the general public doesn't look at
them.  Though sometimes clocks will be so far out of time that
automatic systems abort trying to set them.  Windows has got better at
managing itself over a daylights savings change, but still stuffs it up
under some circumstances.  For some people they won't care that the
computer's clock is mis-set, until things they want to do over the
internet foul up.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.76.1.el7.x86_64 #1 SMP Wed Aug 10 16:21:17 UTC 2022 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

StrongCryptoSettings3 Setting Test Day

[Sumantro Mukherjee]

Hey All,

We have a bunch of test days coming up, we are currently running
StrongCryptoSettings3 test day. I will be keeping this open for
community members to come and test. It's fairly simple, just run the
commands you find in[0] and your output should correspond to [1]

This is an *unconventional* test day which means, two things
1. You must try out any exotic VPN, git work flow, chat apps and see
if they work
2. Anything which will use OpenSSL will be affected and any corner
case should be possibly tested!

The first set of quick command execution will be easy. The test day
matrix will be open for the time being and it will be great to have
this tested!

[0] 
https://fedoraproject.org/wiki/Test_Day:2022-09-05_StrongCryptoSettings3#How_to_test?
[1] https://pagure.io/fedora-qa/issue/707#comment-813926



-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: "Dummy output" instead of sound card options, was working, now gone.

[stan via users]

On Sun, 4 Sep 2022 14:44:11 -0400
Ted Roche  wrote:

> On Sun, Sep 4, 2022 at 1:19 AM stan via users
>  wrote:
> >
> > On Sat, 3 Sep 2022 11:19:27 -0400
> > Ted Roche  wrote:  
> > >
> > > Basic troubleshooting pointers on what to search for would be
> > > appreciated.  
> >
> > aplay -l
> > should show any devices that alsa recognizes.  If alsa doesn't
> > recognize a device, you won't be able to use it.  If alsa knows
> > about the device, I would then use pavucontrol to activate it by
> > setting it as default.  
 
> aplay -l only seems to find HDMI devices:

I think that is your problem.  If alsa doesn't recognize the device,
when it used to, then there is probably a hardware error.  To be sure,
you should check when alsa-lib was installed,
rpm -qi alsa-lib
If that was around the time your device stopped working, it could be a
regression in the library.  They do happen, but it isn't common.  You
can try a downgrade to an earlier alsa-lib by downloading the packages
you have installed from here,
https://koji.fedoraproject.org/koji/packageinfo?packageID=410
and install them with
dnf -C downgrade [list of binary rpms]
in the directory to where you downloaded them.

If it is a discrete sound device, you could try reseating it, in case
it is no longer making good contact.  Do you have another sound device
you can install as a check?

If you run 
journalctl -b0
to look at the last boot, what does it show for sound device
initialization?  Is there any kind of error when it tries to activate
the device that is no longer working?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fstab: systemd still uses the old version

[George N. White III]

On Sun, Sep 4, 2022 at 10:17 AM Robert Nichols 
wrote:

> On 9/3/22 10:21 PM, Robert Nichols wrote:
> > On 8/20/22 6:23 PM, Robert Nichols wrote:
> >> On 8/20/22 4:56 PM, Barry wrote:
> >>>
> >>>
>  On 20 Aug 2022, at 19:16, Robert Nichols 
> wrote:
> 
>  I have added a line to /etc/fstab:
>   /dev/mapper/imgs   /mnt/imgs   ext4  noauto,noexec,nodev  0 0
> 
>  I have run "systemctl daemon-reload"
> 
>  After a reboot, the command "mount /mnt/imgs" still returns the
> message:
>  Mount: (hint) your fstab has been modified, but systemd still uses
> the old version; use 'systemctl daemon-reload' to reload.
> 
>  This is Fedora 36, fully updated.  What am I missing?
> >>>
> >>> I would do an ls -l of the file and check the size and date.
> >>> Does it seems to be changed since the system booted?
> >>>
> >>> Barry
> >>
> >> No, it hasn't been changed, but after yet aother round of
> >> "systemctl daemon-reload; reboot", the message finally went away.
> >>
> >> Thanks for letting me know that what I was doing should be sufficient.
> >
> > Well, it's back, and nothing I do will get rid of that message. I can
> run "systemd daemon-reload" for a temporary fix, but as soon  as I reboot,
> any action such as a remount that references /etc/fstab still results in
> that same "systemd still uses the old version" message.
> >
> > The timestamp shows that /etc/fstab has not been modified since the last
> several reloads. I have run "systemctl daemon-reload" many times since the
> last fstab modification. Do I need to cause that to be run automatically on
> each boot?
> >
> > This is getting annoying.
>
> And, here I am the next morning and everything is working fine with no
> messages.
>
> Here's what I believe must be happening. Because this affected system is
> dual-boot with

MS-Windows, the hardware clock is in local time. During boot, systemd must
> be syncing

/etc/fstab before the system clock has been adjusted to UTC. My timezone
> offset is -5 hours,

so if /etc/fstab was modified less than 5 hours before the reboot, systemd
> will later see it as

"newer" than what it synced.
>

With Windows 10, you should be able to use UTC for the system clock.  The
issue also affects
dual-boot with macOS.   As is often the case, arch linux has the best
documentation:
arch linux has the best documentation
.

I don't fully understand what I just wrote, but that has to be the gist of
> what is happening.
>

> This oddball case of a few warning messages probably isn't worth anyone's
> time to fix.
>

"It is strongly discouraged to set a non-UTC time zone for reasons
including, but not
limited to, time zone confusions, complexities of adjusting clocks for
daylight savings
time depending on regional customs, difficulty in correlating log files
across systems,
possibility of a stale time zone database, and unpredictability, as local
time zones are
subject to arbitrary local policies and laws. " -- Fedora Project
Configuring Time Zone


 For every person who reports a problem like this there are dozens if not
hundreds
who never report the problem.  Many will discover outdated or incorrect
advice from the internet.
Some will decide that linux doesn't work and stick with Windows.

There is a simple and effective solution, but it is buried under a mass of
internet garbage, for example:

itsfoss.com: wrong-time-dual-boot /
mentions "Make Windows use UTC time for the hardware
clock" but the fix is not provided.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Is it possible to convert a live image on a USB to a running system on that same USB

[Michal Schorm]

Hello Terry,

If I understood you correctly, you want to do some modifications to
the LiveOS image.

On Mon, Sep 5, 2022 at 12:56 AM Terry Polzin  wrote:
> To be clear, I don't want to install a disk device.

I'd argue that the operating system installed persistently to the USB
drive by some custom method ensuring only some minimal requested set
of packages is installed would be a better option for most use cases,
also allowing to upgrade the OS to the latest version.
It should also be possible to set up the system in such a way that any
unwanted changes to the system are not saved between reboots.
However I understood from your sentence above that you don't want to
take this approach.

> Thanks for any pointers.

There is a way to make a custom bootable live image of Fedora.
Every few months someone on these mailing lists asks about it.
You might want to check Fedora mailing list archives for that.

I also found this page that might help you:
https://fedoraproject.org/wiki/LiveOS_image/overlay
Though I'm not sure how up-to-date it is.

In general, I'd suggest 'LiveOS' and 'SquashFS' as keywords for your search.

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Mon, Sep 5, 2022 at 12:56 AM Terry Polzin  wrote:
>
> To be clear, I don't want to install a disk device.
>
> Basically I need a procedure to
>
> Remove the livecd user and disable auto login.
> Keep grub intact on the USB and write it's updates there.
>
> I'm perfectly happy booting the USB via the BIOS.  I am currently testing 
> with the XFCE-live image.
>
> Thanks for any pointers.
>
>
>
>
>
>
>
>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue