Audacity can't play audio on Fedora 32
by Sreyan Chakravarty
Hi,
Audacity is unable to play any sort of audio in Fedora 32 on my HP
Notebook.
I installed Audacity from Gnome Software so pretty sure it is a FlatPak.
Whenever I hit the play button I get:
"Error opening sound device.
Try changing the audio host, playback device and the project sample rate."
I did ask the guys over at the Audacity Forums, but they were, lets say,
less than helpful.
You can find the full details of my thread here:
https://forum.audacityteam.org/viewtopic.php?p=395574
The sound devices listed in Audacity are:
* HDA Intel PCH: HDMI 0 (hw:0.3)
* HDA Intel PCH: HDMI 1 (hw:0.7)
* HDA Intel PCH: HDMI 2 (hw:0.8)
* HDA Intel PCH: HDMI 3 (hw:0.9)
* HDA Intel PCH: HDMI 4 (hw:0.10)
* hdmi
And you can find my "Audio Device Info" from Audacity over here:
https://pastebin.com/raw/icDNX20x
So far no other application has given me any issues with sound, Firefox,
VLC, Rhytmbox all work fine. Its only Audacity that is the oddball.
Since the people at Audacity don't know what is going on, I am asking
you guys.
Let me know if any further diagnostic info is required.
Thanks.
--
Regards,
Sreyan
8 months, 2 weeks
boot/grub
by Patrick Dupre
Hello,
On a multi-boot PC, how grub is updated?
In the past /etc/grub2.cfg was updated.
and now?
It seems that there are 2 tools: bootctl, and efibootmgr
What are the files managed by these tools?
How to understand?
BootCurrent: 000F
Which tool is run after an update of the kernel?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
9 months, 1 week
Prevent locking screen
by Beartooth
How do I tell Fedora (currently 32 fully upgraded) never to lock
the screen??
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is
9 months, 1 week
windows10 disk not showing up
by Neal Becker
Today my wife's windows10 lenovo laptop was not starting normally, cycling through various "repair" screens. It does seem to work at least
minimally though.
I tried booting of my f32 usb stick and thought maybe I could take a look at the SSD. But when I start gnome disks, the internal SSD doesn't
show up! lsblk doesn't show it. I looked through journalctl and saw some reference to ATA1, and I believe some kind of error.
Anyone have any idea what's going on? The SSD is working enough to boot windows and run various things like file manager, so why doesn't it
show in linux?
9 months, 1 week
F32 Upgrade From F31 Produces Never Seen Before Error Message in
Gnome on Xorg and Possibly also KDE.
by Stephen Morris
HI,
I have a config file in /etc/X11/xorg.conf.d to start up DM's on
Xorg in 4K monitor resolution, as in F31 both Xorg and Wayland would
start up in 800x600 resolution and I would then have to minimize then
maximize the VM window for the DM to switch into 4K resolution as I
desired. After upgrading from F31 to F32 (there were lots of issues with
the upgrade that I will detail in other threads), when the Gnome on Xorg
DM starts up (I am using Virtualbox on Wndows 10) I get a message at the
top of the DM screen specifying 'VBOxClient: Failed to Register Resizing
Support'. What exactly does this message mean?
Looking at dmesg I also get lots of the following messages:
[ 2457.520753] Service: Shared Clipboard
[ 2457.532708] Service: Host Version Check
[ 2457.543366] Service: Seamless
[ 2457.568504] Service: Drag and Drop (DnD)
[ 2457.574146] Service: Display SVGA X11
[ 2457.593861] Running service failed: VERR_RESOURCE_BUSY
[ 2458.363216] rfkill: input handler disabled
[ 2476.932326] rfkill: input handler enabled
[ 2477.087703] A fatal guest X Window error occurred. This may just
mean that the Window system was shut down while the client was still runn
[ 2477.088440] A fatal guest X Window error occurred. This may just
mean that the Window system was shut down while the client was still runn
[ 2477.089249] A fatal guest X Window error occurred. This may just
mean that the Window system was shut down while the client was still runn
[ 2477.089476] Terminating threads ...
[ 2477.298103] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.298113] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.306374] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.306386] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.307899] Error waiting for HGCM thread to terminate: VERR_TIMEOUT
[ 2477.530080] Error waiting for X11 thread to terminate: VERR_TIMEOUT
[ 2477.530218] Terminating threads done
[ 2478.064888] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2478.064895] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.487676] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.487683] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.704766] Service: Shared Clipboard
[ 2734.706763] Service: Host Version Check
[ 2734.708109] Shared Clipboard: Starting X11 event thread
[ 2734.709898] Service: Seamless
[ 2734.711912] Service: Drag and Drop (DnD)
[ 2734.714049] Service: Display SVGA X11
[ 2734.716013] VMWARE's ctrl extension is available. Major Opcode is 128.
[ 2734.716183] Worker loop running
[ 2734.716706] Proxy window=6291457, root window=349 ...
[ 2734.716858] Started
[ 2734.716976] 6.1.8_Fedorar137981
[ 2734.717337] Failed to register resizing support, rc=VERR_RESOURCE_BUSY
[ 2734.834519] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.834527] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.878953] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.878961] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2735.068488] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2735.068496] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2736.203451] Service: Shared Clipboard
[ 2736.214513] Service: Host Version Check
[ 2736.257245] Service: Seamless
[ 2736.261294] Service: Drag and Drop (DnD)
[ 2736.262580] Running service failed: VERR_RESOURCE_BUSY
[ 2736.269149] Service: Display SVGA X11
[ 2736.272574] VMWARE's ctrl extension is available. Major Opcode is 128.
[ 2736.273835] Failed to register resizing support, rc=VERR_RESOURCE_BUSY
[ 2736.370194] Running service failed: VERR_RESOURCE_BUSY
[ 2736.612437] rfkill: input handler disabled
[ 2783.634779] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2783.634786] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2815.140895] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2815.140902] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2822.904030] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2822.904038] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
regards,
Steve
9 months, 1 week
Re: Fedora 30 EOL
by Suvayu Ali
On Tue, May 26, 2020 at 4:23 PM Mohan Boddu <mboddu(a)bhujji.com> wrote:
>
> As of the 26th of May 2020, Fedora 30 has reached its end of life for
https://bugzilla.redhat.com/show_bug.cgi?id=1742960
Lately all my bug reports tend to go like this. Are others having the
same experience? I have been using Fedora a long time, and part of
the pleasure was I could contribute to making the distro better. Now
it seems to have reduced to "wait until it fixes itself", how is that
any different from Windows/Mac? It's very disappointing to see the
community aspect of Fedora go down this way while the OS has improved
by so much compared to when I started using Fedora.
--
Suvayu
Open source is the future. It sets us free.
9 months, 1 week
fedora 32 live DVD crashes
by Michael Hennebry
I've trying to run Fedora-Workstation-Live-x86_64-32-1.6.iso
on my HP Compac dc5800 Small Form Factor.
It kernel panics with the message that it attempted to kill init
or that it attempted to kill the idle task.
In the former case, it gives exit code 0x00000009.
For several months,
I've been running Centos 7 with no difficulty in booting,
except for needing acpi=off .
I've needed that on every computer I've ever owned.
I know roughly what it means,
but have no idea why it would matter.
The live DVD, including Troubleshoot, crashes with or without acpi=off .
How do I boot?
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
9 months, 1 week
Re: Restart F32 WiFi on ThinkPad P72
by Samuel Sieb
Bringing this back to the list. The message I'm replying to was too
large for the list, so he sent it directly to me.
On 5/30/20 6:49 PM, Robert G (Doc) Savage wrote:
> The "systemctl -b" output is 4099 lines long, so rummaging around for
> KILL is a tall order. Allow me to suggest a slightly different approach.
It's actually quite easy. If you run "systemctl -b" just like that, it
pipes the output to "less" for you to use. In there, you can press the
"/" key and enter the text you want to search for. You can type "1G" to
go to the top and "G" to go to the bottom. See the man page for details.
> Here's the output of "journalctl -b -u NetworkManager". This gives me
> the names of the network devices that NetworkManager knows:
That's not really useful. I was trying to get the info from the wifi
device being initialized.
> When I disconnect the copper Ethernet cable and let NetworkManager try
> to switch over to the WiFi port (normal operation -- both ports cannot
> be open at the same time), five more lines are added to the "journalctl
That's not normal. Normally you can have both ethernet and wifi
connected at the same time. But for some reason, your laptop has a
physical wifi disable when the ethernet cable is plugged in.
> In the old days one would expect this will make it possible to use "ifup
> ATTxxxxxxx" to bring up the WiFi interface. However, when I try this I
> still get:
>
> # ifup ATTxxxxxxx
> Error: Connection activation failed: No suitable device found for this
> connection (device eth0 not available because profile is not compatible
> with device (mismatching interface name)).
>
> For reference, here's the contents of ifcfg-ATTxxxxxxx:
What does "nmcli c show ATTxxxxxxx" give?
> When I left click on the NetworkManager applet in the top MATE toolbar,
> it tells me:
>
> WiFi Networks
>
> *device not manage**d*
>
> Now I gotta ask, how can a WiFi device wlan0 defined as MODE=managed be
> considered not managed by NetworkManager??
It's the connection that you saw is managed, not the device. What do
"nmcli d" and "nmcli d show wlan0" give?
> Incidentally, regarding your questions about Windows operation. The
> answer appears to be the same as in F32. If I'm running eth0, then wlan0
> is disabled and vice versa.
Ok, so that confirms that it really is a hardware switch connected to
the ethernet port. I've never seen that before, it's really weird.
9 months, 1 week
f31 :: sd card not accesible
by Adrian Sevcenco
Hi! I have a very strange situaion with a sandisk extreme sd card:
while in windows i can use it just fine in f31 i have the following:
lsblk shows :
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 59.5G 0 disk
dmesg says:
[ 641.162507] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 641.367806] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[ 641.367869] ldm_validate_partition_table(): Disk read failed.
and trying to make a part table:
parted -s -a optimal /dev/mmcblk0 mklabel msdos
Error: Input/output error during read on /dev/mmcblk0
Error: Input/output error during write on /dev/mmcblk0
so, anyone any idea what is going on? seriosly, linux cannot do what windows can???
Thank you!
Adrian
9 months, 1 week