users July 2020

users@lists.fedoraproject.org

110 participants
114 discussions

Seeing over 3000 Format UTF8_STRING not supported in message log??
by Michael D. Setzer II 02 Jul '20

02 Jul '20

Was looking at message log, and find a ton of these messages? journal[2993]: Failed to store clipboard: Format UTF8_STRING not supported Checked process msetzer+ 2993 1037 2 Jun23 ? 04:44:32 /usr/bin/gnome-shell msetzer+ 3156 2993 0 Jun23 ? 00:00:13 ibus-daemon --panel disable -r --xim Not sure what is causing the message or why the UTF8 not being supported. Generally scan the log now and then, so never saw this before?? Also, see this, but it is only a few? clipit-startup.desktop[3331]: Clipboard is null, recovering ... Thanks.

2 1

xxdiff missing from F32
by Frank Elsner 02 Jul '20

02 Jul '20

Hi, I've fresh install of F32 and cannot install xxdiff which is missing from repos: # dnf install xxdiff Last metadata expiration check: 0:52:40 ago on Thu 02 Jul 2020 01:25:14 PM CEST. No match for argument: xxdiff Error: Unable to find a match: xxdiff A F32 system which was upgraded from F31 has xxdiff installed. What happened to xxdiff? Stay healthy, Frank Elsner

5 5

North Bridge Disconnect?
by Thomas Dineen 02 Jul '20

02 Jul '20

Gentle People: I am developing an optimization application that uses the CPU quite intensely for long periods of time on a CentOS 6.9 machine. Some test runs can run for hours or even days. On a particular test the the OS crashes to a black screen with the message "North Bridge Disconnected" printed in the upper left. The application is carefully designed to not simply consume too much memory and run out, and observation of the System Monitor confirms this. What could be the cause? Is this a bug in my code, quite possible given the fact that I an still testing and debugging? Can a bug in a user application get into Kernel space and crash the machine? Or is it likely a hardware problem on the Motherboard? Thomas Dineen

3 2

Audacity: "Error opening recording device"
by Matti Pulkkinen 01 Jul '20

01 Jul '20

Hello, I'm trying to use Audacity to record the line in on my PC, but I always get the following error: Error opening recording device. Error code: -9997 Invalid sample rate Sounds like an easy-to-fix problem, but the same thing happens regardless of what sample rate I choose. Checking with "pacmd list-sinks" I found that the sample rate for my card is 44100 Hz, so that's what I'm trying to use now that I've checked all possible sample rate options Audacity offers. Also, Audacity offers a bunch of different recording devices with names along the lines of "HDA Intel PCH: ALC892 Alt Analog (hw:0,2): Front Mic:0" but the same error happens with all of them too. Based on what I could find online, it seems like people have had this issue mostly on Windows, and then it was to do with either not having updated drivers or having set the device's sample rate incorrectly. Has anyone here run into something like this before on Fedora? Any ideas where to start trying to fix this? -- Terveisin / Regards, Matti Pulkkinen

8 16