F36Beta Workstation on qemu cannot retun from timeout
I just installed the F36 Workstation Beta. Everything seems to be working just fine. I worked on some other stuff. After a while I returned to the F36Beta. The screen was blank (black) with only a cursor in the display. So, I could find no way to resume my session. Have others seen this issue? -- Did 황준호 die? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: zram0 issue on F35 Beta
On 28/10/2021 22:56, Kamil Paral wrote: On Thu, Oct 28, 2021 at 10:30 AM Joachim Backes wrote: Hi, I'rm running F35 Beta, and I saw the following systemtl message concerning the zram0 device: . . . Oct 28 10:15:29 eule systemd[1]: dev-zram0.swap: Job dev-zram0.swap/start failed with result 'dependency'. Oct 28 10:15:29 eule systemd[1]: Dependency failed for Compressed Swap on /dev/zram0. Oct 28 10:15:29 eule systemd[1]: Failed to start Create swap on /dev/zram0. Oct 28 10:15:29 eule systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'exit-code'. Oct 28 10:15:29 eule systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=exited, status=1/FAILURE Oct 28 10:15:29 eule zram-generator[42576]: Device or resource busy (os error 16) Oct 28 10:15:29 eule zram-generator[42576]: Caused by: Oct 28 10:15:29 eule zram-generator[42576]: Error: Failed to configure disk size into /sys/block/zram0/disksize Oct 28 10:15:29 eule systemd[1]: Starting Create swap on /dev/zram0... Oct 28 10:15:29 eule systemd[1]: Starting Hostname Service... Oct 28 10:15:29 eule audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hostnamed> Oct 28 10:15:29 eule audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-zram-setu> You need to update to this: https://bodhi.fedoraproject.org/updates/FEDORA-2021-82a48ba538 Looks like it isn't available yet, At least not to all mirrors. [egreshko@acer ~]$ sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA -2021-a8034992a9 Fedora 35 - x86_64 - Test Updates 17 kB/s | 11 kB 00:00 Fedora 35 - x86_64 - Test Updates 862 kB/s | 6.2 MB 00:07 Last metadata expiration check: 0:00:16 ago on Fri Oct 29 07:18:31 2021. No security updates needed, but 316 updates available Dependencies resolved. Nothing to do. Complete! -- On Facebook it is called Vaguebooking. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: zram0 issue on F35 Beta
On 28/10/2021 16:28, Joachim Backes wrote: Hi, I'rm running F35 Beta, and I saw the following systemtl message concerning the zram0 device: . . . Oct 28 10:15:29 eule systemd[1]: dev-zram0.swap: Job dev-zram0.swap/start failed with result 'dependency'. Oct 28 10:15:29 eule systemd[1]: Dependency failed for Compressed Swap on /dev/zram0. Oct 28 10:15:29 eule systemd[1]: Failed to start Create swap on /dev/zram0. Oct 28 10:15:29 eule systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'exit-code'. Oct 28 10:15:29 eule systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=exited, status=1/FAILURE Oct 28 10:15:29 eule zram-generator[42576]: Device or resource busy (os error 16) Oct 28 10:15:29 eule zram-generator[42576]: Caused by: Oct 28 10:15:29 eule zram-generator[42576]: Error: Failed to configure disk size into /sys/block/zram0/disksize Oct 28 10:15:29 eule systemd[1]: Starting Create swap on /dev/zram0... Oct 28 10:15:29 eule systemd[1]: Starting Hostname Service... Oct 28 10:15:29 eule audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hostnamed> Oct 28 10:15:29 eule audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-zram-setu> . . . My current kernel is 5.14.14-300.fc35.x86_64. Somebody has similar issues? I'm currently only running F35 on systems that were upgraded from F34. Is yours a fresh install from the RC1.2 live image? What is the output of systemctl status systemd-zram-setup@zram0.service -- On Facebook it is called Vaguebooking. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A rawhide observation
On 14/07/2021 00:29, Adam Williamson wrote: On Sun, 2021-07-11 at 09:47 +0800, Ed Greshko wrote: I'm not formally testing rawhide and the latest kernel. However, my current rawhide VM had become messed up (my fault) so I decided to create a new rawhide VM. So, I downloaded and installed from Fedora-Workstation-Live-x86_64-Rawhide-20210706.n.0.iso in a qemu VM. All went well. However, I did find that if the VM"s video is set to using QXL it is impossible to get back to screen when the screensaver is activated. I just get a blank screen and no mouse clicks or keyboard clicks get me to a screen to enter the user's password. QXL is selected by default when creating the VM on my F34 system. Setting the video to virtio is OK. What component would be best to report this against? I think virtio is actually "more supported" these days, so one option would be to report against libvirt (I think) and suggest we have that as the default... OK, I've done that. https://bugzilla.redhat.com/show_bug.cgi?id=1982133 -- Remind me to ignore comments which aren't germane to the thread. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
A rawhide observation
I'm not formally testing rawhide and the latest kernel. However, my current rawhide VM had become messed up (my fault) so I decided to create a new rawhide VM. So, I downloaded and installed from Fedora-Workstation-Live-x86_64-Rawhide-20210706.n.0.iso in a qemu VM. All went well. However, I did find that if the VM"s video is set to using QXL it is impossible to get back to screen when the screensaver is activated. I just get a blank screen and no mouse clicks or keyboard clicks get me to a screen to enter the user's password. QXL is selected by default when creating the VM on my F34 system. Setting the video to virtio is OK. What component would be best to report this against? -- Remind me to ignore comments which aren't germane to the thread. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: problems upgrading from Fedora 33 to Fedora 34
On 02/05/2021 07:00, Samuel Sieb wrote: "dnf system-upgrade log" will give you a list of available upgrade logs. I don't know what the command to read a specific log is since I don't have any handy right now to test. dnf system-upgrade log --number=X -- Remind me to ignore comments which aren't germane to the thread. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: problems upgrading from Fedora 33 to Fedora 34
On 30/04/2021 20:29, Joachim Backes wrote: On 4/30/21 1:13 PM, Thomas Mittelstaedt wrote: Have you checked the logs with journalctl? Gruß, Thomas Mittelstaedt Thank you. Is there any text in the system journal I should search for? Regards and "Danke" I don't know if this helps at all But after doing the dnf system-upgrade reboot the kernel selection is, of course, for the F33 kernel. But the journal for that boot then shows Apr 30 08:35:19 meimei.greshko.com dnf[722]: Last metadata expiration check: 0:35:51 ago on Fri 30 Apr 2021 07:59:28 AM CST. Apr 30 08:35:19 meimei.greshko.com python3[722]: Starting system upgrade. This will take a while. Apr 30 08:35:38 meimei.greshko.com dnf[722]: Dependencies resolved. and so on. -- Remind me to ignore comments which aren't germane to the thread. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: wi-fi question
On 29/03/2021 03:03, stan via test wrote: This. There is a command that the user can run after the update, and it will find all of these and present them to the user with a little mini menu with single letter commands The command you reference is rpmconf. -- Remind me to ignore comments which aren't germane to the thread. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Rawhide / Firefox / Gmail
On 19/03/2021 02:44, David wrote: This issue is not yet an issue that bothers me enough to investigate any further. Then there is Zero need to mention it. -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A little introduction, and a problem I'm having
On 18/03/2021 15:21, dileepa.tissera dileepa.tissera wrote: You read my mind, I failed a bug against Pipewire just a few minutes ago, hopefully in the right way. For the record, what is the Bugzilla Number? -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A little introduction, and a problem I'm having
On 18/03/2021 15:21, dileepa.tissera dileepa.tissera wrote: You read my mind, I failed a bug against Pipewire just a few minutes ago, hopefully in the right way. For the record, what is the Bugzilla Number? -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A personal story - Rawhide related
On 16/03/2021 13:16, David wrote: I seem to have lots of duplicate packages with the same name: one being F34 and the other F35. dnf [options] remove --duplicates Removes older versions of duplicate packages. To ensure the in‐ tegrity of the system it reinstalls the newest package. In some cases the command cannot resolve conflicts. In such cases the dnf shell command with remove --duplicates and upgrade dnf-shell sub-commands could help. -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Unable to install Fedora-34-20210228.n.0 to VMware Workstation
On 03/03/2021 11:40, Ashish Kumar wrote: I am trying to install Fedora-34-20210228.n.0 on a VMware workstation. It boots fine to the installation menu but after that, I lost my mouse and keyboard control in VM. Anyone else facing similar issues? Booted Fedora-Workstation-Live-x86_64-34-20210228.n.0.iso and currently installing to disk in a qemu VM with no apparent issues. Opened a terminal during the install process with no issue. -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F34 i3 Spin
On 01/03/2021 22:10, Ben Cotton wrote: On Mon, Mar 1, 2021 at 2:12 AM Ed Greshko wrote: Is there a place where issues related to this spin are tracked/recorded? The SIG has an issue tracker at: https://pagure.io/i3-sig/Fedora-i3-Spin/issues They also provide some guidance in the docs: https://docs.fedoraproject.org/en-US/i3/bugs/ I just tried to boot Fedora-i3-Live-x86_64-34-20210227.n.0.iso in a qemu VM and it halts with lightdm failing to start. Looks like this was already reported: https://pagure.io/i3-sig/Fedora-i3-Spin/issue/44 Thanks for those. More generally, I think a Bugzilla against the appropriate component is generally the right place to start for failures in specific components (as opposed to bugs with the integrated result). I have lengthy opinions about bug tracking that I will save for another time. :-) I get the picture. :-) :-) -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F34 i3 Spin
Is there a place where issues related to this spin are tracked/recorded? I just tried to boot Fedora-i3-Live-x86_64-34-20210227.n.0.iso in a qemu VM and it halts with lightdm failing to start. -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F34 KDE Spin on VM Display Size
On 13/02/2021 08:07, Ed Greshko wrote: I'm running F33 KDE host with virt-manager-3.2.0-2.fc33. I've installed F33 KDE spin and F34 KDE spin using the F33 profile when creating the F34 VM. When logging into a session I use Plasma on X11. When running the F33 VM and opening the VM console from virt-manager the display size is automatically resized as the console window is resized. In F33 VM, xrandr returns (for example) [egreshko@f33k ~]$ xrandr Screen 0: minimum 320 x 200, current 1906 x 1292, maximum 8192 x 8192 Virtual-0 connected primary 1906x1292+0+0 0mm x 0mm 1906x1292 59.97*+ 2560x1600 59.99 59.97 1920x1440 60.00 In F34 VM, xrandr returns this, no matter what the console window size is. Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 Virtual-0 connected primary 1024x768+0+0 0mm x 0mm 1024x768 60.00*+ 2560x1600 59.99 59.97 1920x1440 60.00 If I use system-settings in KDE and try to select a larger display size the screen momentarialy shows larger but then reverts to 1024x768 How can I get a larger console in F34 like I did with F33? Well, it appears to be an "sddm" issue. I am able to resize the display to something reasonable if I use Virtio as the Video Card. I also installed F34 Workstation and it performed as desired. So, I installed gdm on the KDE spin and it too can now auto-resize as desired. -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F34 KDE Spin on VM Display Size
I'm running F33 KDE host with virt-manager-3.2.0-2.fc33. I've installed F33 KDE spin and F34 KDE spin using the F33 profile when creating the F34 VM. When logging into a session I use Plasma on X11. When running the F33 VM and opening the VM console from virt-manager the display size is automatically resized as the console window is resized. In F33 VM, xrandr returns (for example) [egreshko@f33k ~]$ xrandr Screen 0: minimum 320 x 200, current 1906 x 1292, maximum 8192 x 8192 Virtual-0 connected primary 1906x1292+0+0 0mm x 0mm 1906x1292 59.97*+ 2560x1600 59.9959.97 1920x1440 60.00 In F34 VM, xrandr returns this, no matter what the console window size is. Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 Virtual-0 connected primary 1024x768+0+0 0mm x 0mm 1024x768 60.00*+ 2560x1600 59.9959.97 1920x1440 60.00 If I use system-settings in KDE and try to select a larger display size the screen momentarialy shows larger but then reverts to 1024x768 How can I get a larger console in F34 like I did with F33? -- People who believe they don't make mistakes have already made one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: firewall applet bug
On 14/01/2021 16:49, Samuel Sieb wrote: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*) is significant in the Wayland case? That one is possible, since by the name, it's related to the system tray. I would also note that the applet works in a KDE/Plasma Wayland session and does not output that bit of info when started from the command line. --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: firewall applet bug
On 14/01/2021 16:22, Samuel Sieb wrote: On 1/13/21 11:07 PM, Ed Greshko wrote: On 14/01/2021 13:54, Samuel Sieb wrote: Application icons stopped being generally supported in Gnome a few releases ago. Have you tried installing gnome-shell-extension-topicons-plus? FWIW, it took me 2 minutes to find that does work for Xorg but not for a Wayland session. Strange, it works for me in Wayland. (not the firewall applet which I've never used, but other ones) I don't use Gnome all that much. I'm a bit confused by the wording of your comment. I think you're saying other items which should appear on the upper bar do show in both Xorg and Wayland sessions. But, not the firewall applet. Which you to have tried? So, maybe QSocketNotifier: Can only be used with threads started with QThread "/proc/4050/root" QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*) is significant in the Wayland case? --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: firewall applet bug
On 14/01/2021 13:54, Samuel Sieb wrote: Application icons stopped being generally supported in Gnome a few releases ago. Have you tried installing gnome-shell-extension-topicons-plus? FWIW, it took me 2 minutes to find that does work for Xorg but not for a Wayland session. --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: firewall applet bug
On 13/01/2021 21:15, pmkel...@frontier.com wrote: The firewall applet bug I originally posted about a year ago hasn't received much attention except for the Fedora version being updated. At this point the bug report is a bit messy. Today I decided to look around a bit and see if I could find some more information. The basic problem is that it doesn't show up on the screen though System Monitor shows the process running and it doesn't cause any Abrt errors. Today I poked around in the logs a bit and found the following: Jan 9 07:36:56 firewall-applet: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*) Jan 9 07:36:56 firewall-applet: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*) Jan 9 07:36:54 firewall-applet: "/proc/1989/root" Jan 9 07:36:53 firewall-applet: QSocketNotifier: Can only be used with threads started with QThread My question is: Should I close this bug and write a new one with this new information, or just add this to the existing bug. I'm wondering if this bug is reported against the correct Fedora component/package/module. https://bugzilla.redhat.com/show_bug.cgi?id=1791860 The bug is still present in fully updated F33 Workstation. I don't have an opinion about if a new BZ needs to be opened. I just wanted to note that the applet fails to show up in both Xorg and Wayland sessions. With Wayland... [egreshko@f33g ~]$ firewall-applet QSocketNotifier: Can only be used with threads started with QThread "/proc/6474/root" QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*) With Xorg [egreshko@f33g ~]$ firewall-applet "/proc/4895/root" So, it seems to me, the Q* messages may not be relevant. --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Display sizing - plasma wayland vs gnome wayland
I have rawhide installed in a kvm vm. Both plasma and gnome desktops are installed and sddm is the DM. After logging in to a gnome session the screen will resize to fill whatever the VM's window is. No matter if the VM's window is a standard resolution or not. When logging into a plasma-wayland session the screen will not resized and one has to use the display settings to pick a "close enough" resolution. This is so, even though the sddm login screen fills the non-standard display size. Additionally, a non-wayland plasma session does what gnome does and what I believe is the preferred behavior. Would I be correct in thinking that this would be a bugzilla against kwin-wayland? --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 keyboard problems
On 28/10/2020 18:51, Joachim Backes wrote: I upgraded almost successfully from F32 to F33, using dnf. Before the upgrade action, my Keyboard was German, with no deadkeys as option, in all Fedora versions. But now, each time I logout and relogin, my keyboard is reset to an STD US keyboard. Is this a known issue? I am running as desktop a CINNAMON desktop. How can I get rid from this problem? I'll include my answer from the user's list just for completeness. Well, if you never use the US keyboard setting there is a "hammer" way to get around the issue. You can remove the US entry from the keyboard layout and leave only de-nodeadkeys. --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: FC33 beta thunder-bird access to smtp tls v1
On 21/10/2020 03:29, Peter Robinson wrote: On Tue, Oct 20, 2020 at 8:23 PM William John Murray wrote: Dear fedora, Any suggestions for things to check? For me this is a blocker on fc33... Probably set the crypto policy to legacy: update-crypto-policies --set LEGACY When it comes to T-Bird and TLSv1 this may be of value https://superuser.com/questions/1586652/thunderbird-78-wont-connect-to-exchange-backed-imap-account --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 testing request: bluetooth mice
On 15/10/2020 01:03, Peter Robinson wrote: A new proposed blocker bug showed up today: https://bugzilla.redhat.com/show_bug.cgi?id=1874082 the issue is that if you have a bluetooth mouse working, then suspend the system, when you resume the bluetooth mouse will not be working any more. You have to go into the GNOME Bluetooth settings applet to get it to work again. So far we have two reports, but they happened to have the exact same mouse. Can other folks who have bluetooth mice (and even, perhaps, other bluetooth hardware - keyboards, headsets?) - ideally different ones! - please test this and report their findings either here or to the bug? It's important to know what range of hardware this affects. The problem here is it could be very hardware/firmware dependent, not just for the mouse but the controller as well. I have seen issues across a bunch of BT devices that don't happen on others and that can be very out of our control. I would second that observation. I've got a Logitech M557 BT Mouse. On an Acer Laptop it will not auto reconnect when the system is rebooted. I have to issue a "bluetoothctl connect" command. However, when the same mouse is used on my HP Tower system it reconnects just fine. This observation is on an F32 KDE spin. --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
F33 Grub Administration Changes?
On previous versions and versions updated to F33 I would see the following. [egreshko@meimei ~]$ sudo grub2-editenv list saved_entry=a48313ea54924eef8eca07a507b7541f-5.8.13-200.fc32.x86_64 boot_success=1 boot_indeterminate=0 kernelopts=root=UUID=4455f2e9-fed2-4e1e-856d-642b531547f9 ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 nomodeset So, I could use grub2-editenv to modify the kernelopts line. However, now with a fresh install of an F33 system I see [egreshko@f33k ~]$ sudo grub2-editenv list saved_entry=8b511c4b483b4414b7bf742b35809e2c-5.8.14-300.fc33.x86_64 boot_success=0 boot_indeterminate=0 Is there a new way to modify the kernel options? The "saved_entry" format is slightly different as well with the "options"line. For F32 options $kernelopts For F33 options root=UUID=e1664725-d90c-4a19-b1d6-86eca7cba8a7 ro rootflags=subvol=root rhgb quiet Seems to me the previous way has advantages? --- The key to getting good answers is to ask good questions. --- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Thunderbird - Unpleasant Surprise
In testing the upcoming F33 release I noticed that it has included thunderbird-78.3.1-1. I decided that I wanted to test the newest TBird but didn't want to go through the process of setting up accounts. So, I downloaded this new release from F32 updates-testing. What could go wrong? IMHO, big mistake. I found that none of the extensions that I use with thunderbird-68.11.0-1 are compatible with the version 78. This includes Enigmail. I was also unable to get calendar working. With TBird 68 I have a local calendar as well as 3 synced Google calendars. I switched back to using 68 and had to figure out how to get my calendars back. In addition, the update to version 78 managed to delete all the entries in my address book. I do nightly backups so it was easy to recover. I wonder if I've done something out of the ordinary or if other users will run into similar pain. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-27 23:50, Chris Murphy wrote: > > DATA/COMPR is the actual compression ratio > DATA/TOTAL is the effective compression ratio, which includes a bit of > overhead and fragmentation of the zram device (the difference between > COMPR and TOTAL) Thanks. > > I suspect zram-fraction=0.75 also would have succeeded. But it's fine > to leave it set to 1.0. And as these are VMs mainly for testing, you > could even set it to 2.0, and see if you run into issues. I did previously run with 0.75 and while it ran longer it did crash before completion. I'll give 2.0 a try in the coming days. If anything interesting occurs I'll post back. > The other reason for caps for systems with more memory, is the zram > device does have a bit of overhead. It's cheap and worth it if the > zram device is being utilized. But it's a waste, however small, if the > zram device isn't being used. In your case, it'd be used so you could > test with a fraction anywhere between 0.5 and 2.0. If you don't want > to test it, 1.0 is pretty safe. > OK. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-27 09:38, Chris Murphy wrote: >> [egreshko@localhost ~]$ zramctl >> NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT >> /dev/zram0 lzo-rle 1.2G 510.6M 159.7M 167.6M 1 [SWAP] > Effective compression ratio is 3:1. Also, that's at the low end of > what I regularly see. High end 4:1. I don't know how to interpret the above to come up with a compression ration. When I first boot the system with no GUI login I see below after an ssh to the system. [egreshko@f33g ~]$ uptime ; zramctl 17:50:18 up 0 min, 1 user, load average: 1.89, 0.55, 0.19 NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 1.2G 4K 74B 12K 1 [SWAP] A bit later on I login from the console and start a gnome-terminal session [egreshko@f33g ~]$ uptime ; zramctl 17:56:13 up 6 min, 2 users, load average: 0.63, 0.45, 0.23 NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 1.2G 137M 42.9M 46M 1 [SWAP] And after doing sudo dnf --refresh check-update later on, I now see [egreshko@f33g ~]$ uptime ; zramctl 18:09:41 up 20 min, 2 users, load average: 0.07, 0.04, 0.09 NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 1.2G 184.9M 61.4M 64.7M 1 [SWAP] -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-27 06:28, Chris Murphy wrote: >>> We are considering bumping the default size for swaponzram. So (b) is >>> helpful to see if there are any negative side effects long term. I >>> never saw any, but I am not a sufficient sample size. >>> >>> Once the installation is finished, you can copy that same .conf file >>> to /mnt/sysimage/etc/systemd/ in the installation environment, so it >>> takes effect upon reboot. >> I'll do this soon. It may be delayed a day or so due to previous >> commitments. Is that OK? > Yeah no hurry. > My morning unexpectedly opened up. Doing the above allowed the installation to complete with 1248mb of memory assigned to the VM. The system booted and is running fine. [egreshko@localhost ~]$ zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 1.2G 510.6M 159.7M 167.6M 1 [SWAP] -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-27 06:28, Chris Murphy wrote: > On Wed, Aug 26, 2020 at 4:00 PM Ed Greshko wrote: >> On 2020-08-27 01:13, Chris Murphy wrote: >>> On Tue, Aug 25, 2020 at 7:55 PM Ed Greshko wrote: >>>> I performed the above after assigning 1248mb and the install completed >>>> fine. >>> (a) create a swap partition in Custom partitioning >>> (b) create a custom /etc/systemd/zram-generator.conf file that uses >>> zram-fraction=1.0, and restart the zram swap service as previously >>> described. >> Just to be clear, you want both a 1248mb swap partition and custom zram. >> Then do the install. > Nope. Just create the zram.generator.conf with zram-fraction=1.0 and > do an automatic install (no swap partition) OK. Since I already had done "a" I was confused. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-27 01:13, Chris Murphy wrote: > On Tue, Aug 25, 2020 at 7:55 PM Ed Greshko wrote: >> I performed the above after assigning 1248mb and the install completed fine. > (a) create a swap partition in Custom partitioning > (b) create a custom /etc/systemd/zram-generator.conf file that uses > zram-fraction=1.0, and restart the zram swap service as previously > described. Just to be clear, you want both a 1248mb swap partition and custom zram. Then do the install. > We are considering bumping the default size for swaponzram. So (b) is > helpful to see if there are any negative side effects long term. I > never saw any, but I am not a sufficient sample size. > > Once the installation is finished, you can copy that same .conf file > to /mnt/sysimage/etc/systemd/ in the installation environment, so it > takes effect upon reboot. I'll do this soon. It may be delayed a day or so due to previous commitments. Is that OK? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-26 02:27, Chris Murphy wrote: > It's getting clobbered by earlyoom. It really doesn't have enough > memory if it's swapping out 892M. If that were on disk, it'd be kindof > a dreadful experience performance wise, but yeah it would eventually > succeed if big enough. I'm not concerned with performance. The F32 installs took time too. But it isn't as if I was in a hurry. These VM's are mostly only used to duplicate issues others are having on the users list. So, install time and user experience are irrelevant, to me. > Another test would be to use Custom partitioning to create disk-based > swap equal to the amount of memory. To do that: keep the btrfs scheme > and have it create the layout for you, then reduce the Btrfs partition > (click on / or /home, and on the right side UI find 'Volume' and click > the Modify button, use fixed size and set a value - now you can create > swap same size as RAM). I performed the above after assigning 1248mb and the install completed fine. My suggestion would be that if the install process could detect/know that it is below the limits needed it would notify the user and not proceed. That is, not just crash. > I'm curious how much swap it ends up using but it'll probably be more > than 800M in which case, it's just seriously under resourced. > > Still another test, you can keep increasing the zram device size up to > 2x memory, i.e. ' zram-fraction=2.0' That has its own consequences but > will still be way faster than disk based swap. Speed isn't the issue, for me. It is crashing v.s. not crashing -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-25 22:35, Kamil Paral wrote: > On Tue, Aug 25, 2020 at 8:33 AM Ed Greshko <mailto:ed.gres...@greshko.com>> wrote: > > Aug 25 02:27:15 localhost-live anaconda[2042]: program: stderr: > Aug 25 02:27:14 localhost-live anaconda[2042]: program: Running... umount > /run/install/source > Aug 25 02:27:13 localhost-live earlyoom[1015]: sending SIGTERM to process > 2042 uid 0 "anaconda": ba > dness 77, VmRSS 55 MiB > Aug 25 02:27:12 localhost-live earlyoom[1015]: low memory! at or below > SIGTERM limits: mem 4.00%, > swap 10.00% > Aug 25 02:27:12 localhost-live earlyoom[1015]: mem avail: 44 of 1191 > MiB ( 3.77%), swap free: > 0 of 892 MiB ( 0.00%) > > So, it would seem, zram based swap is less forgiving than disk based swap. > > > It's not "less forgiving", it's just smaller. The log shows you're out of > memory and out of swap space. If you absolutely need to install on a system > with so little memory, configure a disk-based swap of appropriate size to > compensate for low available memory. Or you can also try to use a netinst > image which has lower memory requirements than a Live desktop image. > Right. In my case I simply increased the memory allocated to the VM for the install process and then lowered it for the running system. These are just "test" VMs and won't have much of a workload. I just need to be able to run multiple VMs at the same time on a host with 6GB. I simply hadn't had an issue before. Being a "long time" user I tend not to read release notes. (Shame, shame) And even then I don't think there are F33 release notes available. I feel the documentation of the F33 equivalent of https://docs.fedoraproject.org/en-US/fedora/f32/release-notes/welcome/Hardware_Overview/ should be more explicit in pointing out installs will fail on systems with less than 2GB. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-25 22:38, Kamil Paral wrote: > On Tue, Aug 25, 2020 at 9:08 AM Ed Greshko <mailto:ed.gres...@greshko.com>> wrote: > > On reflection, I don't think that previous installs without zram used any > swap. > > > That seems hardly possible, according to your logs. Anything is possible, but > it is very improbable that previously you'd be able to finish the > installation without using the disk swap. It's easy to test it. Take Fedora > 32 image of the same kind, and run an installation, but remove all swap-based > partitions in custom disk partitioning first. You'll see if it can finish or > not. > You're most likely correct. I had not thought about that. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-25 14:32, Ed Greshko wrote: > So, it would seem, zram based swap is less forgiving than disk based swap. That may have been silly statement. On reflection, I don't think that previous installs without zram used any swap. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F33 install minimum memory requirements?
On 2020-08-25 13:58, Chris Murphy wrote: > On Mon, Aug 24, 2020 at 11:30 PM Ed Greshko wrote: >> With F32 and previous versions I've been able to install Workstation and >> other spins in a QEMU VM >> with about 1200MB~1248MB of memory. With F33 the install process crashes >> during the "installing software" >> phase. >> >> Is this expected? >> >> FWIW, the "Everything-netinst" install of a KDE system did install just fine >> with 1248MB assigned. >> >> Currently using... >> >> Fedora-Everything-netinst-x86_64-33-20200824.n.0.iso >> Fedora-Workstation-Live-x86_64-33-20200824.n.0.iso >> Fedora-KDE-Live-x86_64-33-20200824.n.0.iso > Are there any hints why it crashed in the journal? That is pretty > tight memory wise. Minimum RAM 2G is what's listed on getfedora.org, > and 4G i s recommended. The biggest difference memory wise I can think > of between F32 and F33 is no disk based swap by default. It uses zram > based swap. And in such a tight case, only 50% may not be enough. > > Even before the zram change though, I'd see ~250M of swap used with a > 2G VM. So that means it's already under provisioned, and walking on > thin ice. > > But we should make sure we have a complete explanation before making > adjustments. You could see if zram set to 75% and 100% help, just as > an extra data point. Create /etc/systemd/zram-generator.conf and edit > to include > > [zram0] > zram-fraction=0.75 > > and then 'systemctl restart swap-create@zram0' > > confirm with swapon and/or zramctl that its size is 75% that of totalmemory > > You can do this prior to beginning the installation. > OK, doing the above still resulted in a crash. But, it happened later in the process. The journal did show Aug 25 02:27:15 localhost-live anaconda[2042]: program: stderr: Aug 25 02:27:14 localhost-live anaconda[2042]: program: Running... umount /run/install/source Aug 25 02:27:13 localhost-live earlyoom[1015]: sending SIGTERM to process 2042 uid 0 "anaconda": ba dness 77, VmRSS 55 MiB Aug 25 02:27:12 localhost-live earlyoom[1015]: low memory! at or below SIGTERM limits: mem 4.00%, swap 10.00% Aug 25 02:27:12 localhost-live earlyoom[1015]: mem avail: 44 of 1191 MiB ( 3.77%), swap free: 0 of 892 MiB ( 0.00%) So, it would seem, zram based swap is less forgiving than disk based swap. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
F33 install minimum memory requirements?
With F32 and previous versions I've been able to install Workstation and other spins in a QEMU VM with about 1200MB~1248MB of memory. With F33 the install process crashes during the "installing software" phase. Is this expected? FWIW, the "Everything-netinst" install of a KDE system did install just fine with 1248MB assigned. Currently using... Fedora-Everything-netinst-x86_64-33-20200824.n.0.iso Fedora-Workstation-Live-x86_64-33-20200824.n.0.iso Fedora-KDE-Live-x86_64-33-20200824.n.0.iso -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Some issues when running cinnamon desktop with F32
On 2020-04-30 23:03, Ed Greshko wrote: > I see. I will be doing the upgrade in the morning. I assume you're running > lightdm? I ask since > there seems to have been a change in gdm that was brought up on the users > list. The location of > the icon to pick the DE was moved to the lower right corner and was > overlooked. I did the upgrade this am 1. I still don't know what the switchdesk is suppose to accomplish. I've not used it before can't say if it should/shouldn't work. 2. No problem with the login manager (lightdm). I can login to a cinnamon or Xfce desktop. How about testing with sddm or gdm? I used to know where the list of available DE are kept, but I forgot. 3. I got the F32 background after the upgrade. 4. And, no problems with Thunderbird. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Some issues when running cinnamon desktop with F32
On 2020-04-30 22:40, Joachim Backes wrote: > > > On 2020-04-30 16:25, Ed Greshko wrote: >> On 2020-04-30 20:52, Joachim Backes wrote: >>>> In your initial post you said >>>> >>>> 1. The switchdesk gnome command offers only gnome as desktop. But setting >>>> from cinnamon to gnome will be without effect. >>>> >>>> Do you recall if it worked for you correctly in F31? >>> Yes! >>>> I just finished the F31 install and the switchdesk GUI >>>> is offering "Xfce" and "default". >>>> >>>> >>>> >>> Did you try to start Xfce *after additionally* restarting X11 (after >>> switchdesk...?) >> I suppose I don't know what switchdesk is supposed to accomplish. After >> selecting Xfce in >> switchdesk and rebooting a login brought up Cinnamon. >> >> I had to manually select Xfce at the login screen to bring it up. > > This was the case in F31. In F32, there is only the option to display the > password in the login screen", but > no selection of the desktop! I see. I will be doing the upgrade in the morning. I assume you're running lightdm? I ask since there seems to have been a change in gdm that was brought up on the users list. The location of the icon to pick the DE was moved to the lower right corner and was overlooked. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Some issues when running cinnamon desktop with F32
On 2020-04-30 20:52, Joachim Backes wrote: >> In your initial post you said >> >> 1. The switchdesk gnome command offers only gnome as desktop. But setting >> from cinnamon to gnome will be without effect. >> >> Do you recall if it worked for you correctly in F31? > > Yes! >> I just finished the F31 install and the switchdesk GUI >> is offering "Xfce" and "default". >> >> >> > Did you try to start Xfce *after additionally* restarting X11 (after > switchdesk...?) I suppose I don't know what switchdesk is supposed to accomplish. After selecting Xfce in switchdesk and rebooting a login brought up Cinnamon. I had to manually select Xfce at the login screen to bring it up. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Some issues when running cinnamon desktop with F32
On 2020-04-30 18:42, Joachim Backes wrote: > > > On 2020-04-30 12:25, Ed Greshko wrote: >> On 2020-04-30 18:21, Joachim Backes wrote: >>> >>> >>> On 2020-04-30 11:29, Ed Greshko wrote: >>>> On 2020-04-30 17:17, Joachim Backes wrote: >>>>> Dear F32 users, >>>>> >>>>> After having installed F32 (previously F31 with cinnamon) , some issues: >>>> A bit of clarification please. >>>> >>>> Is this an upgrade of F31 to F32 or a new F32 install? >>>> If an upgrade, was this an F31 Cinnamon installed with added desktops? If >>>> so, which ones? >>> >>> a) It was an upgrade >>> b) Previously Cinnamon was installed, additionally Xfce >> >> OK, I'll try to reproduce. It may take a bit as it is late in the day here. >> :-) >> >> > In your initial post you said 1. The switchdesk gnome command offers only gnome as desktop. But setting from cinnamon to gnome will be without effect. Do you recall if it worked for you correctly in F31? I just finished the F31 install and the switchdesk GUI is offering "Xfce" and "default". -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Some issues when running cinnamon desktop with F32
On 2020-04-30 17:17, Joachim Backes wrote: > Dear F32 users, > > After having installed F32 (previously F31 with cinnamon) , some issues: A bit of clarification please. Is this an upgrade of F31 to F32 or a new F32 install? If an upgrade, was this an F31 Cinnamon installed with added desktops? If so, which ones? > > 1. The switchdesk gnome command offers only gnome as desktop. But setting > from cinnamon to gnome will be without effect > 2. The login manager does no more present the selection of any installed > destkop type (for example xfce aso.) > 3. No new background for F32 (Cinnamon is started with F31 desktop bg > 4. Thunderbird: if the main window has more new mails then its height, the > slider in the presented vertical scrollbar is unvisible > > Anybody has similar problems? Any help will be appreciated > > -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: NetworkManager down eno2
On 2020-04-27 09:43, Samuel Sieb wrote: > On 4/26/20 6:22 PM, ToddAndMargo via test wrote: >> On 2020-04-26 14:48, ToddAndMargo via test wrote: >> > > "dnf remove network-scripts" >> >> And I just put it back in as qemu-kvm requires it >> to do bridge networking (br0) > > I use kvm with bridge networking and I don't have network-scripts installed. > Same here virsh # iface-dumpxml virbr0 -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
F32 and the 5.6 kernel
I'd been doing all of my F32 testing on VM's. Today I decided that since F32 is GO that I'd start upgrading my bare metal systems. I don't recall if I raised the issue here but I had been having an issue on F31 after an update to the 5.5 kernel. Power Saving wasn't working as expected under KDE. The monitor didn't enter power saving as quickly as it did. On "wake-up" the monitor came alive but things appeared frozen with no visible cursor. After a few more seconds the screen would blink and then all was normal. Anyway, happy to report that the 5.6 kernel has fixed that. Oh, and the entire upgrade process went as smooth as silk. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: a Rawhide error message
On 2020-04-24 13:57, David wrote: > I do not think I have ever seen this error message before. > > Should I reboot, or wait for another update ? > > > Verifying : userspace-rcu-0.12.1-1.fc33.x86_64 > 73/78 > Verifying : userspace-rcu-0.12.0-1.fc33.x86_64 > 74/78 > Verifying : kernel-5.7.0-0.rc1.20200414git8632e9b5645b.1.fc33. > 75/78 > Verifying : kernel-core-5.7.0-0.rc1.20200414git8632e9b5645b.1. > 76/78 > Verifying : kernel-modules-5.7.0-0.rc1.20200414git8632e9b5645b > 77/78 > Verifying : kernel-modules-extra-5.7.0-0.rc1.20200414git8632e9 > 78/78 > Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row > failed: database disk image is malformed > This isn't something that will be fixed by an update. This is the database which is queried when running commands like "dnf history". It is also the database which is updated when dnf transactions are performed. Have you by chance run out of disk space? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Cura Lulzbot ??
On 2020-04-23 22:31, David wrote: > D | Command line | Date and time | Action(s) | > Altered > > 12 | install *-firmware | 2020-04-08 13:09 | Install | 74 Well, the 12 would indicate the package wasn't added at install time. So, do sudo dnf history info 12 And you will find that *-firmware matches lulzbot-marlin-firmware which then installed cura-lulzbot as a dependency as well as a whole bunch of other stuff you probably didn't notice. Now, hope you can see the unintended consequences of using * and not checking what is going to be installed before hitting "y". You should also be reading the dnf man page to learn more of how it works. > > On Thu, Apr 23, 2020 at 1:33 AM Ed Greshko <mailto:ed.gres...@greshko.com>> wrote: > > On 2020-04-23 14:00, David wrote: > > This is probably a dumb question, but how did Cura Lulzbot get > > on my Rawhide install ? > > What does > > sudo dnf history list cura-lulzbot > > return? > -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Cura Lulzbot ??
On 2020-04-23 14:00, David wrote: > This is probably a dumb question, but how did Cura Lulzbot get > on my Rawhide install ? What does sudo dnf history list cura-lulzbot return? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Brave blocking upgrade
On 2020-04-22 11:49, ToddAndMargo via test wrote: > On 2020-04-21 19:32, Ed Greshko wrote: >> >> >> On Wed, Apr 22, 2020, 09:41 ToddAndMargo via test >> mailto:test@lists.fedoraproject.org>> wrote: >> >> On 2020-04-21 18:36, Ed Greshko wrote: >> > On 2020-04-22 08:21, ToddAndMargo via test wrote: >> >> Now the 64,000 dollar question is, is this a bug >> >> or normal operation? >> > >> > It is an issue for the Brave distribution to address. Not >> related to Fedora. >> > >> >> So, rpm was not suppose to overwrite the key? >> Sound a lot like an rpm bug to me. >> >> >> You will recall that the public key in installed as a separate act. > > Not to beat a dead horse, but was that act performed by > "rpm" (a Fedora package) suppose to have overwritten > the previous key or just existed without an error > message? No. Software packaged in the RPM format isn't by definition "Fedora". RedHat did write the RPMstandard but it is used buy lots of folks to package their Software. This includes Suse, RPMFusion,and Brave. It is up to the person creating the specific package to determine the actions taken duringinstall, upgrade, erasure. The public keys are used to check the signatures of the rpm packagers. They are normally controlled by a separate function. In the case of Fedora itself you have fedora-gpg-keys-31-3.noarch. Name : fedora-gpg-keys Version : 31 Release : 3 Architecture : noarch Size : 101 k Source : fedora-repos-31-3.src.rpm Repository : @System From repo : updates Summary : Fedora RPM keys URL : https://fedoraproject.org/ License : MIT Description : This package provides the RPM signature keys. In the case of RPMFusion, there are multiple. One is rpmfusion-free-release. Name : rpmfusion-free-release Version : 31 Release : 1 Architecture : noarch Size : 8.7 k Source : rpmfusion-free-release-31-1.src.rpm Repository : @System From repo : rpmfusion-free Summary : RPM Fusion (free) Repository Configuration URL : http://rpmfusion.org License : BSD Description : RPM Fusion free package repository files for yum and dnf : along with gpg public keys It doesn't appear that Brave does the same. It also isn't necessary, and seldom are old key removed as they are unique. I should have told you thatit was not necessary to erase the old Brave key as the old and the new had totally different names. So, running sudo rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc Would have added gpg-pubkey-c2d4e821-5e7252b8 in addition to the older one c2d4e821-5d13a788 > >> >> Both the act of installing the key as well as the brave-browser are not >> supplied or supported by the Fedora Community. > > This is why my question is about the behavior of rpm not Brave The behavior of "rpm" is defined by the person/project. The Brave project, IMO, is deficient in this area. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Brave blocking upgrade
On Wed, Apr 22, 2020, 09:41 ToddAndMargo via test < test@lists.fedoraproject.org> wrote: > On 2020-04-21 18:36, Ed Greshko wrote: > > On 2020-04-22 08:21, ToddAndMargo via test wrote: > >> Now the 64,000 dollar question is, is this a bug > >> or normal operation? > > > > It is an issue for the Brave distribution to address. Not related to > Fedora. > > > > So, rpm was not suppose to overwrite the key? > Sound a lot like an rpm bug to me. > You will recall that the public key in installed as a separate act. Both the act of installing the key as well as the brave-browser are not supplied or supported by the Fedora Community. > ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Brave blocking upgrade
On 2020-04-22 08:21, ToddAndMargo via test wrote: > Now the 64,000 dollar question is, is this a bug > or normal operation? It is an issue for the Brave distribution to address. Not related to Fedora. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Brave blocking upgrade
On 2020-04-19 04:58, ToddAndMargo via test wrote: > Dear Testers, > > To get FC32 to upgrade on one of my VM's, I have to add > --disablerepo=brave* > > to the following: > > #dnf --enablerepo=* update --refresh --disablerepo=brave* > ... > # dnf system-upgrade download --refresh --releasever=32 --allowerasing --best > --disablerepo=brave* > > I opened: > > GPG check FAILED on RPM installation with Fedora 32 > https://github.com/brave/brave-browser/issues/9315 I checked that open issue. It doesn't appear as any action has been taken since it shows Assignees No one assigned Labels None yet Projects None yet Milestone No milestone Linked pull requests Successfully merging a pull request may close this issue. None yet I did the following 1. Installed Brave on a fully updated F31 VM. No Problems 2. Installed Brave on a fully updated F32 Beta VM. No Problems 3. Upgraded the F31 VM by doing sudo dnf system-upgrade download --releasever=32 And the upgrade succeeded without problems. You may want to run your test again. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: problems to run vboxconfig [VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64] under kernel 5.6.3-300.fc31.x86_64
On 2020-04-10 18:19, Joachim Backes wrote: > Hi , > > today I installed kernel-5.6.3-300.fc31.x86_64 (from Koji). It runs, but > having the problem to get running vboxconfig (from > VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64): > > vboxdrv.sh: Stopping VirtualBox services. > vboxdrv.sh: Starting VirtualBox services. > vboxdrv.sh: Building VirtualBox kernel modules. > vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went > wrong. > > There were problems setting up VirtualBox. To re-start the set-up process, > run > /sbin/vboxconfig > as root. If your system is using EFI Secure Boot you may need to sign the > kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load > them. > > No probs when using kernel-5.5.16 > > Anybody has experience in solving this problem? Are these relevant? https://www.virtualbox.org/ticket/19312 https://www.virtualbox.org/ticket/19450 -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: sort of Rawhide related
On 2020-04-09 00:47, Adam Williamson wrote: > On Tue, 2020-04-07 at 21:34 -0500, David wrote: >> >> I am sending this email using this new install. > Glad it's working for you. Thanks for testing! It is good to test. But, I hope the OP does more than just blog about his experience. He needs to "engage" if he wishes to advance beyond novice. He asked a question on the "users" list and when asked to supply more information didn't respond. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: A personal usage report
On 2020-03-17 19:03, David wrote: > Do any Fedora users out there prefer the simpler default menu ? > Seriously, this is a "test" list. Not a general discussion on what people like or don't like about a desktop. That type of "general audience" question is more appropriate on the "users" list. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F32 Beta KDE shutdown takes too long
On 2020-03-17 07:12, Ed Greshko wrote: > On 2020-03-17 00:30, Kamil Paral wrote: >> If you can submit a negative karma as well, that's appreciated. Next time, >> if you spot such an issue, and the software is still in testing, please >> submit a negative karma asap, so that the broken update doesn't reach >> regular users. Thanks! > Oh, I did just give negative karma to the F31 version. > Oh, bugger... I inadvertently tested on an F32 system which had been upgraded from F31 but still marked as F31. It didn't fail when tested in an actual F31VM. So, this version only exhibits a problem with F32. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F32 Beta KDE shutdown takes too long
On 2020-03-17 00:30, Kamil Paral wrote: > On Sun, Mar 15, 2020 at 12:03 PM Ed Greshko <mailto:ed.gres...@greshko.com>> wrote: > > On 2020-03-15 16:53, Ed Greshko wrote: > > In testing the just released F32 Beta in a QEMU/KVM, installed from > Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too > long. It pauses for 1min 30seconds for a stopped job. The journal shows. > > > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: > spice-vdagentd.service: State 'stop-sigterm' timed out. Killing. > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: > spice-vdagentd.service: Killing process 1146 (spice-vdagentd) with signal > SIGKILL. > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: > spice-vdagentd.service: Main process exited, code=killed, status=9/KILL > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: > spice-vdagentd.service: Failed with result 'timeout'. > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: > Stopped Agent daemon for Spice guests. > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> audit[1]: > SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=spice-vdagentd comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: > Stopped target Basic System. > > > > is this a known problem? > > > > > > I just noticed that spice-vdagent was upgraded after the install. > > Downgrading from spice-vdagent-0.20.0-1.fc32 to spice-vdagent-0.19.0-5 > resolves the issue. > > I have created https://bugzilla.redhat.com/show_bug.cgi?id=1813667 > > > Thanks Ed, for debugging this and reporting the issue. I can reproduce it, so > I commented on the bug and also posted negative karma on that spice-vdagent > update: > https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ff500948d > > If you can submit a negative karma as well, that's appreciated. Next time, if > you spot such an issue, and the software is still in testing, please submit a > negative karma asap, so that the broken update doesn't reach regular users. > Thanks! Ah, yes. Thanks for reminding me about that. Unfortunately it seems I should not have slept. "Comments and Feedback are Closed" -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F32 Beta KDE shutdown takes too long
On 2020-03-17 00:30, Kamil Paral wrote: > If you can submit a negative karma as well, that's appreciated. Next time, if > you spot such an issue, and the software is still in testing, please submit a > negative karma asap, so that the broken update doesn't reach regular users. > Thanks! Oh, I did just give negative karma to the F31 version. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: F32 Beta KDE shutdown takes too long
On 2020-03-15 16:53, Ed Greshko wrote: > In testing the just released F32 Beta in a QEMU/KVM, installed from > Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too > long. It pauses for 1min 30seconds for a stopped job. The journal shows. > > Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: State > 'stop-sigterm' timed out. Killing. > Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Killing > process 1146 (spice-vdagentd) with signal SIGKILL. > Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Main > process exited, code=killed, status=9/KILL > Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Failed > with result 'timeout'. > Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped Agent daemon for Spice > guests. > Mar 15 16:46:25 f32k.greshko.com audit[1]: SERVICE_STOP pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=spice-vdagentd comm="systemd" exe="/usr/lib/systemd/systemd" > hostname=? addr=? terminal=? res=failed' > Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped target Basic System. > > is this a known problem? > > I just noticed that spice-vdagent was upgraded after the install. Downgrading from spice-vdagent-0.20.0-1.fc32 to spice-vdagent-0.19.0-5 resolves the issue. I have created https://bugzilla.redhat.com/show_bug.cgi?id=1813667 -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
F32 Beta KDE shutdown takes too long
In testing the just released F32 Beta in a QEMU/KVM, installed from Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too long. It pauses for 1min 30seconds for a stopped job. The journal shows. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: State 'stop-sigterm' timed out. Killing. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Killing process 1146 (spice-vdagentd) with signal SIGKILL. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Main process exited, code=killed, status=9/KILL Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Failed with result 'timeout'. Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped Agent daemon for Spice guests. Mar 15 16:46:25 f32k.greshko.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spice-vdagentd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped target Basic System. is this a known problem? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: f32 upgrade breaks mdns/avahi
On 2020-03-08 17:58, Chris Murphy wrote: > Hi, > > $ ssh chris@fnuc.local > > Works on F31. Fails on F32 *upgrade*. Works on F32 clean. > > Best I can tell is something is modifying /etc/nsswitch.conf during the > upgrade. > > Before dnf system-upgrade (and clean) > hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname > > After dnf system-upgrade (only): > hosts: files dns myhostname > > If I restore this, and restart avahi-daemon.service, the ssh command > works again. > > Dunno a good way to find out what touches this file in offline upgrade > mode. Maybe if I chattr +i then whatever tries to modify it will fail > and complain into the journal? Or maybe auditd is running in offline > updates? > OK, I just did an upgrade from an F31 system and observe the same situation. There now exists... [egreshko@f31k6 etc]$ ls nsswitch.conf* nsswitch.conf nsswitch.conf.bak nsswitch.conf.rpmnew -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: f32 upgrade breaks mdns/avahi
On 2020-03-08 17:58, Chris Murphy wrote: > Hi, > > $ ssh chris@fnuc.local > > Works on F31. Fails on F32 *upgrade*. Works on F32 clean. > > Best I can tell is something is modifying /etc/nsswitch.conf during the > upgrade. > > Before dnf system-upgrade (and clean) > hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname > > After dnf system-upgrade (only): > hosts: files dns myhostname > > If I restore this, and restart avahi-daemon.service, the ssh command > works again. > > Dunno a good way to find out what touches this file in offline upgrade > mode. Maybe if I chattr +i then whatever tries to modify it will fail > and complain into the journal? Or maybe auditd is running in offline > updates? > > FWIW, I have not yet performed an upgrade from F31 to F32. However, I would like to note that on an install of F32 from Fedora-KDE-Live-x86_64-32-20200228.n.0.iso and subsequent updates I have [egreshko@f32k2 etc]$ ll nsswitch.conf* lrwxrwxrwx. 1 root root 29 Mar 7 15:17 nsswitch.conf -> /etc/authselect/nsswitch.conf -rw-r--r--. 1 root root 2215 Feb 28 19:41 nsswitch.conf.bak and nsswitch.conf.bak does contain hosts: files dns myhostname -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: question about Rawhide and the unofficial third-party repo
On 2020-03-08 14:04, David wrote: > When Fedora 32 branches off Rawhide, does anything happen to the most > popular unofficial third-party repo ? Please try not to obfuscate. What is the name of the repo you are talking about? > > Does this forum allow for such heresy to talk about the specific repo and its > proprietary packages ? I see some distros refer to these packages as > "tainted." Is that just a polite way of saying, non-free ? It isn't. However, if you have specific questions on what is / is not the state/process of a given repo you should go to their site/forum for that info. And "tainted" is a specific term. See https://www.kernel.org/doc/html/v4.15/admin-guide/tainted-kernels.html In the case of the broadcom drivers the kernel is probably tainted in 3 ways. A module with a non-GPL license has been loaded, this includes modules with no license. An out-of-tree module has been loaded and An unsigned module has been loaded in a kernel supporting module signature > > On a related note, I have an empty PCI slot, I was saving for a graphics card, > but I could instead add a fancy Linux-supported wi-fi card. Which one ? > ASUS AC1200 ?? The product you suggest isn't a wifi card. It is a wifi router. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: requesting wi-fi help
On 2020-03-08 08:45, Samuel Sieb wrote: > On 3/7/20 3:50 PM, Ed Greshko wrote: >> On 2020-03-08 06:19, Samuel Sieb wrote: >>> On 3/7/20 1:57 PM, David wrote: >>>> I am probably asking on the wrong listserve, but this is the only one >>>> I subscribe to. >>> >>> The "users" mailing list would be a much better place for getting help with >>> this kind of question. >> >> But, if memory serves me, David is running "rawhide". So, he may well be >> getting ahead of the curve. > > Good point, I didn't connect the dots. Thank you. > Still, he would probably get more help from the users list anyway for > something like this. > Well, except that poc will redirect him to the test list when he learns he is running rawhide. :-) :-) -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: requesting wi-fi help
On 2020-03-08 06:19, Samuel Sieb wrote: > On 3/7/20 1:57 PM, David wrote: >> I am probably asking on the wrong listserve, but this is the only one >> I subscribe to. > > The "users" mailing list would be a much better place for getting help with > this kind of question. But, if memory serves me, David is running "rawhide". So, he may well be getting ahead of the curve. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Bug report #1804709
On 2020-02-20 00:24, Adam Williamson wrote: > On Wed, 2020-02-19 at 08:02 -0600, Richard Shaw wrote: >> On Wed, Feb 19, 2020 at 7:56 AM Soham Gumaste wrote: >> >>> Hello, >>> (I hope this is the correct list) >>> >> Unfortunately not :) This is the test list which is for unreleased version >> of Fedora but your bug report is for Fedora 31 so the regular user list >> would be a good place for general discussion. > Sorry, no, I don't think that's correct. > > test@ is the QA team list. Discussion of testing of stable releases is > perfectly on-topic here. The description of the list in Hyperkitty / > Mailman is "For testing and quality assurance of Fedora releases" - not > just *pre* releases. > > You *could* talk about this on the users list, but I don't think it's > off topic here at all! > > Soham, looks like Kamil helped you out in the bug report itself. Thanks > for filing it, though. To add a touch of perspective on the matter. If one is new to Fedora and runs into issues it is probably a good idea to ask about the issue on the user's list prior to submitting a bug. Others may have already encountered the issue. Or, even if they haven't, be able to assist in narrowing down the culprit. It may help in resolving the issue quickly without going through a "formal" process. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: gimp segfault
On 2020-01-08 12:47, Richard Ryniker wrote: > Can anyone report success to run gimp in Rawhide? I see its splash > screen, a few messages about initialization, then a segfault. Fails in the same way here in a VM. > > Full stack trace at: http://ryniker.org/Fedora/gimp_stack_trace > > > GNU Image Manipulation Program version 2.10.14 > git-describe: GIMP_2_10_12-511-ga4f55d6c7e > C compiler: > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/9/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none > OFFLOAD_TARGET_DEFAULT=1 > Target: x86_64-redhat-linux > Configured with: ../configure --enable-bootstrap > --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared > --enable-threads=posix --enable-checking=release --enable-multilib > --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions > --enable-gnu-unique-object --enable-linker-build-id > --with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin > --enable-initfini-array --with-isl --enable-offload-targets=nvptx-none > --without-cuda-driver --enable-gnu-indirect-function --enable-cet > --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux > Thread model: posix > gcc version 9.2.1 20190827 (Red Hat 9.2.1-1) (GCC) > > using babl version 0.1.72 (compiled against version 0.1.72) > using GEGL version 0.4.18 (compiled against version 0.4.18) > using GLib version 2.63.3 (compiled against version 2.63.0) > using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) > using GTK+ version 2.24.32 (compiled against version 2.24.32) > using Pango version 1.44.7 (compiled against version 1.44.7) > using Fontconfig version 2.13.92 (compiled against version 2.13.92) > using Cairo version 1.16.0 (compiled against version 1.16.0) > > ``` >> fatal error: Segmentation fault > Stack trace: > ``` > > # Stack traces obtained from PID 6432 - Thread 6432 # > > [New LWP 6435] > [New LWP 6436] > [New LWP 6437] > [New LWP 6438] > [New LWP 6439] > [New LWP 6440] > [New LWP 6441] > [New LWP 6442] > [New LWP 6443] > [New LWP 6444] > [New LWP 6445] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > __libc_read (nbytes=256, buf=0x7ffef7a5b890, fd=14) at > ../sysdeps/unix/sysv/linux/read.c:26 > 26 return SYSCALL_CANCEL (read, fd, buf, nbytes); > Id Target Id Frame > * 1Thread 0x7f7629f8cdc0 (LWP 6432) "gimp-2.10" __libc_read > (nbytes=256, buf=0x7ffef7a5b890, fd=14) at > ../sysdeps/unix/sysv/linux/read.c:26 > 2Thread 0x7f761cd60700 (LWP 6435) "worker" syscall () at > ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 > 3Thread 0x7f761c55f700 (LWP 6436) "worker" syscall () at > ../sysdeps/unix/sysv/linux/x86_64/sysc > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-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/test@lists.fedoraproject.org -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: pipewire
On 2019-12-05 04:53, pmkel...@frontier.com wrote: > I have just recently become aware of pipewire. If my questions are the wrong > ones please feel free to interpret them in a more correct way. I am wondering: > > Is pipewire part of Wayland? > > From what I've seen so far, it seems like pipewire will replace gstreamer, > ffmpeg, pulse audio, and jack. Though all of the changes are apparently being > implemented over a longish period of time. Is all of the audio and video > stream software being replaced by pipewire? > > Is there a block diagram or something else somewhere so I can see how these > fit into an audio or video stream for now and with pipewire later? Does their wiki help? https://github.com/PipeWire/pipewire/wiki -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Available to test install
On 2019-12-01 09:06, Robert Moskowitz wrote: > Kind of. > > I just put together the notebook I will be using when F32 ships. It is a > Lenovo X140e, 8GB memory, and a 500GB SSD. > > It was an EDU series and I *THINK* I have the bios set right. Defaulting to > first UEFI boot now rather than Legacy first. > > I do have limited time, but I am willing to download a network installer ISO > and put the current build with Xfce for the gui. > > Plus testing mounting my Samsung Galaxy S4 which won't mount with F30 (though > worked fine with F28). > > Plus the constant crashing of Thunar whenever I mount an SD card. I do > wonder if I installed with the wrong UEFI setting.. > > Anyway, I do have limited time, but I can carve out some, now that the system > is sitting here on my desk. > > Let me know and the URL for a current build. As far as I know F32 has not yet been "branched". Had it been, it would be found here. https://kojipkgs.fedoraproject.org/compose/branched/ So, if you want to use something not F31 you'll have be be content with Rawhide. https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/compose/Spins/x86_64/iso/ -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: libgit2-0.28* are inexplicably excluded in F31
On 10/29/19 8:03 AM, Felix Miata wrote: - package libgit2-0.28.3-1.fc31.i686 is excluded - package libgit2-0.28.3-1.fc31.x86_64 is excluded excludes may also be placed in repo files. Did you check those? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/27/19 1:26 AM, Adam Williamson wrote: Filing a new bug wouldn't hurt, for sure. Thanks. Probably against dnf- plugins-extras . Apparently it has already been done. https://bugzilla.redhat.com/show_bug.cgi?id=1764169 -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/20/19 10:59 PM, Adam Williamson wrote: On Sun, 2019-10-20 at 06:56 +0800, Ed Greshko wrote: On 10/18/19 2:31 PM, Ed Greshko wrote: On 10/18/19 2:05 PM, Adam Williamson wrote: I might need more logs from your case to be sure of what's going on - if you could put the dnf logs and system journals up somewhere it'd help. Also, did you re-run the download phase after updating the system-upgrade plugin? You do need to do that... Yes, I ran "dnf system-upgrade clean" as well as "dnf clean packages" for good measure. The change I put in last week fixes the case I diagnosed, but I mean it's still possible there's some other case where the transactions come up different for sure. Will need data to figure it out though. OK journal is at https://drive.google.com/open?id=1qCUyZcC5-QjE83uh9p5wC10tIai1PCO2 dnf log is at https://drive.google.com/file/d/1K17NzRLf8e945kQ1gHKdlFqi2v87IpQb/view?usp=sharing And for the record I have added to https://bugzilla.redhat.com/show_bug.cgi?id=1758588 Sorry Ed, got sidelined by other stuff. But I need the dnf log from the download transaction as well, to compare the two. Can you find that one too? Thanks! As you know, I did supply the requested logs in the BZ. The issue I reported seems either not to have been considered or is irrelevant to 178588. So, I think others may encounter the same issue. Should a new BZ be created? Or, will there be an advisory to erase the offending packages and manually reinstall after the upgrade completes? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/20/19 10:59 PM, Adam Williamson wrote: On Sun, 2019-10-20 at 06:56 +0800, Ed Greshko wrote: On 10/18/19 2:31 PM, Ed Greshko wrote: On 10/18/19 2:05 PM, Adam Williamson wrote: I might need more logs from your case to be sure of what's going on - if you could put the dnf logs and system journals up somewhere it'd help. Also, did you re-run the download phase after updating the system-upgrade plugin? You do need to do that... Yes, I ran "dnf system-upgrade clean" as well as "dnf clean packages" for good measure. The change I put in last week fixes the case I diagnosed, but I mean it's still possible there's some other case where the transactions come up different for sure. Will need data to figure it out though. OK journal is at https://drive.google.com/open?id=1qCUyZcC5-QjE83uh9p5wC10tIai1PCO2 dnf log is at https://drive.google.com/file/d/1K17NzRLf8e945kQ1gHKdlFqi2v87IpQb/view?usp=sharing And for the record I have added to https://bugzilla.redhat.com/show_bug.cgi?id=1758588 Sorry Ed, got sidelined by other stuff. But I need the dnf log from the download transaction as well, to compare the two. Can you find that one too? Thanks! OK I have redone the upgrade and added the logs to the bugzilla. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/18/19 2:31 PM, Ed Greshko wrote: On 10/18/19 2:05 PM, Adam Williamson wrote: I might need more logs from your case to be sure of what's going on - if you could put the dnf logs and system journals up somewhere it'd help. Also, did you re-run the download phase after updating the system-upgrade plugin? You do need to do that... Yes, I ran "dnf system-upgrade clean" as well as "dnf clean packages" for good measure. The change I put in last week fixes the case I diagnosed, but I mean it's still possible there's some other case where the transactions come up different for sure. Will need data to figure it out though. OK journal is at https://drive.google.com/open?id=1qCUyZcC5-QjE83uh9p5wC10tIai1PCO2 dnf log is at https://drive.google.com/file/d/1K17NzRLf8e945kQ1gHKdlFqi2v87IpQb/view?usp=sharing And for the record I have added to https://bugzilla.redhat.com/show_bug.cgi?id=1758588 -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/18/19 2:05 PM, Adam Williamson wrote: I might need more logs from your case to be sure of what's going on - if you could put the dnf logs and system journals up somewhere it'd help. Also, did you re-run the download phase after updating the system-upgrade plugin? You do need to do that... Yes, I ran "dnf system-upgrade clean" as well as "dnf clean packages" for good measure. The change I put in last week fixes the case I diagnosed, but I mean it's still possible there's some other case where the transactions come up different for sure. Will need data to figure it out though. OK journal is at https://drive.google.com/open?id=1qCUyZcC5-QjE83uh9p5wC10tIai1PCO2 dnf log is at https://drive.google.com/file/d/1K17NzRLf8e945kQ1gHKdlFqi2v87IpQb/view?usp=sharing -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/18/19 7:49 AM, Samuel Sieb wrote: One very odd thing here though is that it's looking for fc30 packages. Maybe there is an rpmfusion problem as well since there is no appstream data past 30 yet. Oh, BTW, it is in the 31 repo of rpmfusion it is just not updated in name [root@f31bg ~]# cat /etc/fedora-release Fedora release 31 (Thirty One) [root@f31bg ~]# rpm -q rpmfusion-nonfree-appstream-data rpmfusion-free-appstream-data rpmfusion-nonfree-appstream-data-30-1.20181021.fc30.noarch rpmfusion-free-appstream-data-30-1.20181021.fc30.noarch -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/18/19 7:49 AM, Samuel Sieb wrote: On 10/17/19 4:16 PM, Ed Greshko wrote: Almost there But the problem may not be a "fedora" problem? 2019-10-17T23:09:44Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/rpmfusion-free-058b175644bc1430/packages/rpmfusion-free-appstream-data-30-1.20181021.fc30.noarch.rpm 2019-10-17T23:09:44Z CRITICAL Package "rpmfusion-free-appstream-data-30-1.20181021.fc30.noarch" from repository "rpmfusion-free" has incorrect checksum 2019-10-17T23:09:44Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/rpmfusion-nonfree-c253272f7b309f17/packages/rpmfusion-nonfree-appstream-data-30-1.20181021.fc30.noarch.rpm 2019-10-17T23:09:44Z CRITICAL Package "rpmfusion-nonfree-appstream-data-30-1.20181021.fc30.noarch" from repository "rpmfusion-nonfree" has incorrect checksum 2019-10-17T23:10:11Z DDEBUG Cleaning up. Those referenced files do not exist. That is the symptom of the problem. Did you get the updated plugin? One thing I wondered is what would happen if you manually added the "missing" rpms to the cache directory after the regular download process was complete. It should work. Yes. Got that and did the module reset. python3-dnf-plugin-system-upgrade-4.0.7-1.fc30.noarch One very odd thing here though is that it's looking for fc30 packages. Maybe there is an rpmfusion problem as well since there is no appstream data past 30 yet. Yes, that oddity has me questioning where the problem lies. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/18/19 4:41 AM, Adam Williamson wrote: On Thu, 2019-10-17 at 10:17 -0700, Samuel Sieb wrote: On 10/17/19 2:15 AM, Ed Greshko wrote: The issue seems to be related to 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-desktop-5.16.5-1.fc31.x86_64.rpm There was a recent discussion about this issue and a bug filed, but I don't have the number off-hand. The problem is that when --allow-erasing is used, there is a possibility for dnf to build a slightly different transaction after reboot than it did before. This means that it can't find the rpms that it thinks it should install. Yeah, it is a bug I investigated and fixed last week: https://bugzilla.redhat.com/show_bug.cgi?id=1758588 if you use the updated upgrade plugin from updates-testing the problem would be fixed. HOWEVER, using --allowerasing may not actually be what you want to do. The problem may ultimately be caused by the libgit2 module mess: https://bugzilla.redhat.com/show_bug.cgi?id=1747408 in which case what you should do (AIUI) is run 'dnf module reset libgit2' and then try the system-upgrade download step again, without --allowerasing: it should hopefully work, and not remove any of your packages. Almost there But the problem may not be a "fedora" problem? 2019-10-17T23:09:44Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/rpmfusion-free-058b175644bc1430/packages/rpmfusion-free-appstream-data-30-1.20181021.fc30.noarch.rpm 2019-10-17T23:09:44Z CRITICAL Package "rpmfusion-free-appstream-data-30-1.20181021.fc30.noarch" from repository "rpmfusion-free" has incorrect checksum 2019-10-17T23:09:44Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/rpmfusion-nonfree-c253272f7b309f17/packages/rpmfusion-nonfree-appstream-data-30-1.20181021.fc30.noarch.rpm 2019-10-17T23:09:44Z CRITICAL Package "rpmfusion-nonfree-appstream-data-30-1.20181021.fc30.noarch" from repository "rpmfusion-nonfree" has incorrect checksum 2019-10-17T23:10:11Z DDEBUG Cleaning up. Those referenced files do not exist. -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/17/19 5:58 PM, Ed Greshko wrote: On 10/17/19 5:15 PM, Ed Greshko wrote: Thanks Thrown a bit since dnf.log times are Z tagged. The issue seems to be related to 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-desktop-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-desktop-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-integration-5.16.5-2.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-integration-5.16.5-2.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-lookandfeel-fedora-5.16.5-1.fc31.noarch.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-lookandfeel-fedora-5.16.5-1.fc31.noarch" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-workspace-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-workspace-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-workspace-wayland-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-workspace-wayland-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:53Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/sddm-breeze-5.16.5-1.fc31.noarch.rpm 2019-10-16T23:34:53Z CRITICAL Package "sddm-breeze-5.16.5-1.fc31.noarch" from repository "fedora" has incorrect checksum Will try clean-up and try again No, same issue. FWIW, I'm using dnf --skip-broken --allowerasing system-upgrade download --releasever=31 I suppose it is possible I'm hitting a bad mirror? Well, it seems, adding --allowerasing is a bad idea since none of the packages referenced above are actually getting downloaded. dnf --skip-broken system-upgrade download --releasever=31 isn't any better as it results in Error: Problem 1: package dnf-yum-4.2.11-2.fc30.noarch requires dnf = 4.2.11-2.fc30, but none of the providers can be installed - dnf-4.2.11-2.fc30.noarch does not belong to a distupgrade repository - problem with installed package dnf-yum-4.2.11-2.fc30.noarch Problem 2: problem with installed package kf5-ktexteditor-5.59.0-1.fc30.x86_64 - package kf5-ktexteditor-5.61.0-1.fc31.x86_64 requires libgit2.so.28()(64bit), but none of the providers can be installed - kf5-ktexteditor-5.59.0-1.fc30.x86_64 does not belong to a distupgrade repository - package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is excluded - package libgit2-0.28.3-1.fc31.x86_64 is excluded I suppose waiting may be in order -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/17/19 5:15 PM, Ed Greshko wrote: Thanks Thrown a bit since dnf.log times are Z tagged. The issue seems to be related to 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-desktop-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-desktop-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-integration-5.16.5-2.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-integration-5.16.5-2.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-lookandfeel-fedora-5.16.5-1.fc31.noarch.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-lookandfeel-fedora-5.16.5-1.fc31.noarch" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-workspace-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-workspace-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-workspace-wayland-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-workspace-wayland-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:53Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/sddm-breeze-5.16.5-1.fc31.noarch.rpm 2019-10-16T23:34:53Z CRITICAL Package "sddm-breeze-5.16.5-1.fc31.noarch" from repository "fedora" has incorrect checksum Will try clean-up and try again No, same issue. FWIW, I'm using dnf --skip-broken --allowerasing system-upgrade download --releasever=31 I suppose it is possible I'm hitting a bad mirror? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Upgrade F30-->F31 failing. Were to get more info?
On 10/17/19 2:13 PM, Adam Williamson wrote: On Thu, 2019-10-17 at 07:52 +0800, Ed Greshko wrote: This is the first time I've had issues with an upgrade. Laptop is a fully updated F30 system running only KDE desktop. It is an older Acer Aspire 5920. The package are downloaded and upon "system-upgrade reboot" the system does reboot and a screen saying "updates being installed, don't turn off". After a few minutes the system reboots again but into a normal F30 state. dnf system-upgrade log --number=-1 Oct 17 07:34:57 acer.greshko.com systemd[1]: dnf-system-upgrade.service: Failed with result 'exit-code'. Oct 17 07:34:57 acer.greshko.com systemd[1]: Failed to start System Upgrade using DNF. Where to find more detailed info? journalctl -b-1 and /var/log/dnf.log are a couple of places to start. Thanks Thrown a bit since dnf.log times are Z tagged. The issue seems to be related to 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-desktop-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-desktop-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-integration-5.16.5-2.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-integration-5.16.5-2.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-lookandfeel-fedora-5.16.5-1.fc31.noarch.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-lookandfeel-fedora-5.16.5-1.fc31.noarch" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-workspace-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-workspace-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:50Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/plasma-workspace-wayland-5.16.5-1.fc31.x86_64.rpm 2019-10-16T23:34:50Z CRITICAL Package "plasma-workspace-wayland-5.16.5-1.fc31.x86_64" from repository "fedora" has incorrect checksum 2019-10-16T23:34:53Z CRITICAL Error opening file for checksum: /var/lib/dnf/system-upgrade/fedora-3589ee8a7ee1691d/packages/sddm-breeze-5.16.5-1.fc31.noarch.rpm 2019-10-16T23:34:53Z CRITICAL Package "sddm-breeze-5.16.5-1.fc31.noarch" from repository "fedora" has incorrect checksum Will try clean-up and try again -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Upgrade F30-->F31 failing. Were to get more info?
This is the first time I've had issues with an upgrade. Laptop is a fully updated F30 system running only KDE desktop. It is an older Acer Aspire 5920. The package are downloaded and upon "system-upgrade reboot" the system does reboot and a screen saying "updates being installed, don't turn off". After a few minutes the system reboots again but into a normal F30 state. dnf system-upgrade log --number=-1 Oct 17 07:34:57 acer.greshko.com systemd[1]: dnf-system-upgrade.service: Failed with result 'exit-code'. Oct 17 07:34:57 acer.greshko.com systemd[1]: Failed to start System Upgrade using DNF. Where to find more detailed info? -- The key to getting good answers is to ask good questions. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops
On 8/31/19 1:30 PM, Alessio wrote: > On Sat, Aug 31, 2019, 6:51 AM Ed Greshko <mailto:ed.gres...@greshko.com>> wrote: > > Is this a known issue? I'm guessing it has to do with an Wayland issue > and the VBox Video drivers. However, I don't know how to prove that. > > > Same issue here. > But it should be this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1746563 > > Thanks -- If simple questions can be answered with a simple google query then why are there so many of them? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops
On 8/31/19 12:51 PM, Ed Greshko wrote: > Just started to test F31. The Xfce and KDE spins are going OK. I'm using > VirtualBox-6.0-6.0.10 directly from Oracle on the host. > > Fedora-Workstation-Live-x86_64-31-20190828.n.0.iso boots fine and the Install > to boot completes without error. > > However, when booting to the installed system I get the screen: > > Oh no! Something has gone wrong > A problem has occurred and the system can't recover. > > Is this a known issue? I'm guessing it has to do with an Wayland issue and > the VBox Video drivers. However, I don't know how to prove that. > > Same issue on a QEMU VM. -- If simple questions can be answered with a simple google query then why are there so many of them? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops
Just started to test F31. The Xfce and KDE spins are going OK. I'm using VirtualBox-6.0-6.0.10 directly from Oracle on the host. Fedora-Workstation-Live-x86_64-31-20190828.n.0.iso boots fine and the Install to boot completes without error. However, when booting to the installed system I get the screen: Oh no! Something has gone wrong A problem has occurred and the system can't recover. Is this a known issue? I'm guessing it has to do with an Wayland issue and the VBox Video drivers. However, I don't know how to prove that. -- If simple questions can be answered with a simple google query then why are there so many of them? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: what to install to (eventually) be able to upgrade to fedora 31?
On 8/28/19 7:13 PM, Robert P. J. Day wrote: > On Tue, 27 Aug 2019, Alessio wrote: > >> On Tue, Aug 27, 2019, 7:07 PM Robert P. J. Day wrote: >> >> what is the *proper* ISO to install that will eventually get me to >> fedora 31? thanks. >> >> >> Hello. >> I think you should look here: >> https://kojipkgs.fedoraproject.org/compose/branched/ >> >> Check the STATUS file to see if the building is still in progress. > i'm still curious about the meaning of the STATUS file there, as > what i see currently is: > > COMPOSE_ID = Fedora-31-20190826.n.0 > STATUS = FINISHED_INCOMPLETE > > but if i wander down to find the ISO, i get what appears to be a > perfectly installable: > > Fedora-Workstation-Live-x86_64-31-20190826.n.0.iso > > so i don't know what FINISHED_INCOMPLETE means in the context of what > appears to be a perfectly complete and working ISO. Wasn't this answer in an earlier part of the thread sufficient? DOOMED should mean that something has gone very bad, and no images were produced. FINISHED_INCOMPLETE should mean that not all the expected images have been built. So, if you find the ISO you are looking for, it should boot. So, you found a good Fedora-Workstation-Live ISO, but maybe if you looked for say the Xfce ISO it isn't available or some other ISO that is part of the build. -- If simple questions can be answered with a simple google query then why are there so many of them? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: 30 upgrade does not take
On 4/9/19 9:04 AM, Adam Williamson wrote: > On Mon, 2019-04-08 at 17:13 -0700, ToddAndMargo wrote: >> Hi All, >> >> This is what I am running to upgrade from 29 to 30 beta: >> >> # rpm --rebuilddb >> # rpm -Va --nofiles --nodigest >>if anything is too new, do a >> # dnf downgrade offender(s) (no problems found) >> >> # dnf --enablerepo=* update --refresh >> # dnf install python3-dnf-plugin-system-upgrade >> # dnf system-upgrade download --refresh --releasever=30 --allowerasing >> --best >> # dnf clean packages <-- optional (didn't do it) >> # dnf system-upgrade reboot >> >> >> When I run the "dnf system-upgrade reboot", it reboots, tells >> me an upgrade is on progress, and about five second later, >> reboots again, shows no 30 kernels, and I am back in 29. >> >> What did I do wrong? > Well, you'll want this at least, as per the common bugs page and the > upgrading wiki page: > > dnf system-upgrade download --refresh --releasever=30 > --setopt='module_platform_id=platform:f30' > > See https://fedoraproject.org/wiki/DNF_system_upgrade , > https://fedoraproject.org/wiki/Common_F30_bugs#upgrade-module-platform > and https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1688462 . > > If it still does the same with that, you'll need to check the logs from > the upgrade boot to see what went wrong. After it reboots back to F29, > run 'journalctl -b-1' to see logs from the previous boot (i.e. the > upgrade attempt) and you should be able to find some kind of indication > as to what went wrong. I also wouldn't do "dnf --enablerepo=* update --refresh" as this would enable "updates-testing" and may result in packages not yet upgraded in the F30 world. Also, the OP doesn't indicate if any 3rd party repos are involved. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F30 KDE Spin no Login GUI after update
On 3/23/19 12:07 AM, Rodger Etz wrote: > Sounds like what I see using the F29 KDE spin upgraded to F30 on bare metal > x86_64. > > It seems SDDM is not launching properly via systemd anymore. > > When you switch to another TTY, login and execute > > systemctl stop sddm && sddm > > it starts properly. > > Did a quick strace and saw that something is trying to access some file > without success when launching via systemd. > > Sorry, didn't have time to dive into it and file an issue yet. Thanks. Yes, it may be the BZ Adam refers to. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
F30 KDE Spin no Login GUI after update
I had a running F30 system in a KVM VM. When updating with these latest packages kf5-akonadi-server.x86_64 18.12.2-2.fc30 updates-testing kf5-akonadi-server-mysql.x86_64 18.12.2-2.fc30 updates-testing kf5-frameworkintegration.x86_64 5.55.0-2.fc30 updates-testing kf5-frameworkintegration-libs.x86_64 5.55.0-2.fc30 updates-testing kf5-kdeclarative.x86_64 5.55.0-2.fc30 updates-testing kf5-kwayland.x86_64 5.55.0-2.fc30 updates-testing kf5-kxmlgui.x86_64 5.55.0-2.fc30 updates-testing kwin.x86_64 5.15.2-3.fc30 updates-testing kwin-common.x86_64 5.15.2-3.fc30 updates-testing kwin-libs.x86_64 5.15.2-3.fc30 updates-testing plasma-integration.x86_64 5.15.2-2.fc30 updates-testing qt-settings.noarch 30.0-1.fc30 updates-testing qt5-qdbusviewer.x86_64 5.12.1-1.fc30 updates-testing qt5-qtbase.x86_64 5.12.1-2.fc30 updates-testing qt5-qtbase-common.noarch 5.12.1-2.fc30 updates-testing qt5-qtbase-gui.x86_64 5.12.1-2.fc30 updates-testing qt5-qtbase-mysql.x86_64 5.12.1-2.fc30 updates-testing qt5-qtdeclarative.x86_64 5.12.1-1.fc30 updates-testing qt5-qtgraphicaleffects.x86_64 5.12.1-1.fc30 updates-testing qt5-qtimageformats.x86_64 5.12.1-1.fc30 updates-testing qt5-qtlocation.x86_64 5.12.1-1.fc30 updates-testing qt5-qtmultimedia.x86_64 5.12.1-1.fc30 updates-testing qt5-qtquickcontrols.x86_64 5.12.1-1.fc30 updates-testing qt5-qtquickcontrols2.x86_64 5.12.1-1.fc30 updates-testing qt5-qtscript.x86_64 5.12.1-1.fc30 updates-testing qt5-qtsensors.x86_64 5.12.1-1.fc30 updates-testing qt5-qtspeech.x86_64 5.12.1-1.fc30 updates-testing qt5-qtspeech-speechd.x86_64 5.12.1-1.fc30 updates-testing qt5-qtsvg.x86_64 5.12.1-1.fc30 updates-testing qt5-qttools.x86_64 5.12.1-1.fc30 updates-testing qt5-qttools-common.noarch 5.12.1-1.fc30 updates-testing qt5-qttools-libs-designer.x86_64 5.12.1-1.fc30 updates-testing qt5-qtvirtualkeyboard.x86_64 5.12.1-1.fc30 updates-testing qt5-qtwebchannel.x86_64 5.12.1-1.fc30 updates-testing qt5-qtwebengine.x86_64 5.12.1-1.fc30 updates-testing qt5-qtwebkit.x86_64 5.212.0-0.34.alpha2.fc30 updates-testing qt5-qtx11extras.x86_64 5.12.1-1.fc30 updates-testing qt5-qtxmlpatterns.x86_64 5.12.1-2.fc30 updates-testing sddm.x86_64 0.18.0-6.fc30 updates-testing The system will not go to the login screen. It seems "stuck" with [ OK ] Started Hold until boot process finishes up displayed I can issue Alt-F2 to get to a TTY but I can't see anything obvious. Know issue? -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Test Results:Fedora 29 RC 1.2 Desktop
On 11/1/18 2:51 AM, Lawrence E Graves wrote: > Has anyone notice that rss-glx screensaver will not install because of > missing dependencies. Enable the updates-testing and install from there. -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29 Xfce ibus systray widget?
On 9/28/18 11:26 AM, Robert Moskowitz wrote: > Maybe this is only in the armhfp build, but I have a 'new' widget on my > systray. > About says it is for ibus. > > What is this? Why was it added as a default item with F29. I do not have it > on my > F28 x86_64 notebook. ibus stands for Intelligent Input Bus. A method for multilingual input. We use in on our systems to input Chinese, Japanese, and Korean. Not sure why it would be enabled on your system. On my F29 system it was not enabled by default. To deselect it, you can go to your menu under Applications--->Settings--->Input Method Selector and pick "none" -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
F29 Gnome Install process - A pain
This will probably be considered a "minor" pain. And, since I don't use GNOME except in a VM for testing, I guess it is. I'd just like to go on record to say I dislike a few things about the install process. 1. There is no option to set the hostname during install. 2. User creation is delayed until first boot and at the time of creation there is no option to specify the UID and GID. So, if you're like me, and use existing NFS services and your primary user doesn't have 1000/1000 for them you have to either know to create an initial throw away account or manually make changes later. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/22/18 3:01 AM, Robert Moskowitz wrote: > I can't get vncserver started on my F28-arm image: I never really looked into why, but the "fix" is to comment out the PID entry in the vncserver.service entry. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 11:14 PM, Robert Moskowitz wrote: > > > On 9/21/18 11:02 AM, Ed Greshko wrote: >> On 9/21/18 9:14 PM, Robert Moskowitz wrote: >>> I have had this problem pre beta images. This is the F29-armfhp code base. >>> >>> I am running vnc server as a service. I have edited the xstartup to have: >>> >>> # exec /etc/X11/xinit/xinitrc >>> exec /bin/sh /etc/xdg/xfce4/xinitrc >>> xrdb $HOME/.Xresources >>> startxfce4 & >>> >>> Note that currently, the is no .Xresources file. >> I do not know why you're doing that. But, I haven't. >> >>> When I connect to the system after a fresh boot or vncserver restart I get >>> a dialog >>> with: >>> >>> Error XFCE PolicyKit Agent >>> >>> Ed Greshko reported on the Fedora list (as I thought this was a more general >>> VNC/Xfce error having nothing to do with the beta) that he does not get >>> this error, >>> but he is NOT running vncserver as a service. Rather from an SSH session. >> I have configured by f28 system to run vncsever as a service and I see the >> error >> you're reporting. >> >> I believe I understand why the error is presented. >> >> If you start the vncserver you'll see something like this >> >> polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd >> --no-debug >> egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit >> >> running >> >> When you make a vnc client connection, you get the error and then you'll see >> only >> >> polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd >> --no-debug >> >> running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at >> 23:00. > > My F28 install is right now doing its dnf update which will take a bit. But > I was > setting what starts at startup via Settings > Session and Startup > > And I noticed that polkit is started there. I bet if you turn that off, > things MAY > get better. Of course then console login will not have polkit. So perhaps > vncserver should NOT be running polkit? > > After a bit of testing and a bit of googling the answer is. vncserver and polkit don't play nice when vncserver is started as a service as described in /lib/systemd/system/vncserver@.service. The issue is not confined to Xfce. The same basic problem exists when the spin used in KDE. As mentioned elsewhere, if you ssh into the system and start vncserver manually then everything works "normally" for the most part. It seems nobody has done much to attempt to fix the problem from what I can tell. That being said, a workaround is described here https://forums.fedoraforum.org/showthread.php?316905-PolicyKit-failed-over-headless-VNC=1809280#post1809280 With the other alternative to be having your vnc client (remmina can do it) issue a pre-command via ssh to start the vncserver manually. Of course you'll to have "authorized_keys" on the vncserver system side to make this seamless. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 9:14 PM, Robert Moskowitz wrote: > I have had this problem pre beta images. This is the F29-armfhp code base. > > I am running vnc server as a service. I have edited the xstartup to have: > > # exec /etc/X11/xinit/xinitrc > exec /bin/sh /etc/xdg/xfce4/xinitrc > xrdb $HOME/.Xresources > startxfce4 & > > Note that currently, the is no .Xresources file. I do not know why you're doing that. But, I haven't. > > When I connect to the system after a fresh boot or vncserver restart I get a > dialog > with: > > Error XFCE PolicyKit Agent > > Ed Greshko reported on the Fedora list (as I thought this was a more general > VNC/Xfce error having nothing to do with the beta) that he does not get this > error, > but he is NOT running vncserver as a service. Rather from an SSH session. I have configured by f28 system to run vncsever as a service and I see the error you're reporting. I believe I understand why the error is presented. If you start the vncserver you'll see something like this polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd --no-debug egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit running When you make a vnc client connection, you get the error and then you'll see only polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd --no-debug running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at 23:00. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 9:47 AM, Chris Murphy wrote: > On Thu, Sep 20, 2018 at 6:08 PM Ed Greshko wrote: >> On 9/21/18 7:42 AM, Chris Murphy wrote: >>> On Thu, Sep 20, 2018 at 2:47 PM Samuel Sieb wrote: >>> >>>> That is true, but there is also a reasonable chance or losing them, >>>> breaking them, or other random failures. When a flash drive dies, it's >>>> gone, very difficult to recover if even possible. I would not recommend >>>> a flash drive (or DVD) alone for long-term storage. >>> All CD and DVD consumer burnable (R or RW) are not suitable for long >>> term storage. The dyes used are not gonna very long, maybe a few >>> years. If they're kept in the dark at stable temperature, I'd be >>> surprised if they lasted 5 years. Bluray is a different story, and >>> with proper storage shows some promise of being readable for quite a >>> while, but you're gonna have to put a drive, cables, and a computer >>> into cold storage along with the discs so... good luck. >>> >> FWIW, I think I must be very lucky. I have just checked several of my TDK >> DVD-RW >> disks that were written between 2003 and 2005. >> I'd forgotten all about them until reading this. They've been sitting on >> the top of >> a cabinet that is exposed to indirect sunlight and temp ranges of >> between the 60's and 80's and high humidity. (I fight with my wife about >> the A/C in >> the summer). >> >> All of them read just fine. Which is good since I'd been looking for the >> photos of >> one of our departed cats which were "lost" due to an HD failure. > Yes, lucky. Make copies, quick! > Well, since I did forget about them and it has been 15 years (3X your upper end estimate) I don't think they are that important. I'll check them again in another 15 years. If I have a DVD drive at that time. :-) -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 7:42 AM, Chris Murphy wrote: > On Thu, Sep 20, 2018 at 2:47 PM Samuel Sieb wrote: > >> That is true, but there is also a reasonable chance or losing them, >> breaking them, or other random failures. When a flash drive dies, it's >> gone, very difficult to recover if even possible. I would not recommend >> a flash drive (or DVD) alone for long-term storage. > All CD and DVD consumer burnable (R or RW) are not suitable for long > term storage. The dyes used are not gonna very long, maybe a few > years. If they're kept in the dark at stable temperature, I'd be > surprised if they lasted 5 years. Bluray is a different story, and > with proper storage shows some promise of being readable for quite a > while, but you're gonna have to put a drive, cables, and a computer > into cold storage along with the discs so... good luck. > FWIW, I think I must be very lucky. I have just checked several of my TDK DVD-RW disks that were written between 2003 and 2005. I'd forgotten all about them until reading this. They've been sitting on the top of a cabinet that is exposed to indirect sunlight and temp ranges of between the 60's and 80's and high humidity. (I fight with my wife about the A/C in the summer). All of them read just fine. Which is good since I'd been looking for the photos of one of our departed cats which were "lost" due to an HD failure. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Tracer does not seem to work,..
On 9/19/18 5:28 AM, Robert Moskowitz wrote: > So far tracer has not reported a need to restart anything. I thought there > were a > couple updates that it should have required restarting. > > Can someone else also test this? You may have found something I have 2 VM's. One if F28 the other F29. I installed tracer on both. Both systems were fully updated. On both systems I downgraded firefox. Then I logged into both system and started firefox. After starting ff I did a dnf update. On the F28 system... [root@f28k-b1 ~]# dnf update Last metadata expiration check: 0:09:17 ago on Wed 19 Sep 2018 07:31:35 AM CST. Dependencies resolved. === Package Arch Version Repository Size === Upgrading: firefox x86_64 62.0-2.fc28 updates 89 M Transaction Summary === Upgrade 1 Package Total download size: 89 M Is this ok [y/N]: y Downloading Packages: firefox-62.0-2.fc28.x86_64.rpm 3.7 MB/s | 89 MB 00:23 --- Total 3.6 MB/s | 89 MB 00:25 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: firefox-62.0-2.fc28.x86_64 1/1 Preparing : 1/1 Upgrading : firefox-62.0-2.fc28.x86_64 1/2 Running scriptlet: firefox-62.0-2.fc28.x86_64 1/2 Running scriptlet: firefox-59.0.2-1.fc28.x86_64 2/2 Cleanup : firefox-59.0.2-1.fc28.x86_64 2/2 Running scriptlet: firefox-59.0.2-1.fc28.x86_64 2/2 Running scriptlet: firefox-62.0-2.fc28.x86_64 2/2 Running scriptlet: firefox-59.0.2-1.fc28.x86_64 2/2 Verifying : firefox-62.0-2.fc28.x86_64 1/2 Verifying : firefox-59.0.2-1.fc28.x86_64 2/2 Upgraded: firefox.x86_64 62.0-2.fc28 Complete! [root@f28k-b1 ~]# tracer You should restart: * These applications manually: firefox Then on the F29 system... [root@f29bk ~]# dnf update Last metadata expiration check: 0:07:15 ago on Wed 19 Sep 2018 07:21:13 AM CST. Dependencies resolved. Problem: cannot install the best update candidate for package perl-HTTP-Tiny-0.076-1.fc29.noarch - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is disabled === Package Arch Version Repository Size === Upgrading: firefox x86_64 62.0-3.fc29 updates-testing 87 M Transaction Summary === Upgrade 1 Package Total download size: 87 M Is this ok [y/N]: y Downloading Packages: firefox-62.0-3.fc29.x86_64.rpm 4.5 MB/s | 87 MB 00:19 --- Total 4.1 MB/s | 87 MB 00:21 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: firefox-62.0-3.fc29.x86_64 1/1 Preparing : 1/1 Upgrading : firefox-62.0-3.fc29.x86_64 1/2 Running scriptlet: firefox-62.0-3.fc29.x86_64 1/2 Running scriptlet: firefox-61.0.2-3.fc29.x86_64 2/2 Cleanup : firefox-61.0.2-3.fc29.x86_64 2/2 Running scriptlet: firefox-61.0.2-3.fc29.x86_64 2/2 Running scriptlet: firefox-62.0-3.fc29.x86_64 2/2 Running scriptlet: firefox-61.0.2-3.fc29.x86_64 2/2 Verifying : firefox-62.0-3.fc29.x86_64 1/2 Verifying : firefox-61.0.2-3.fc29.x86_64 2/2 Upgraded: firefox-62.0-3.fc29.x86_64 Complete! [root@f29bk ~]#
F29 and BZ 1627963
Hi, I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1627963 against F28 and I've tested the latest kernel 4.18.7-200 from koji. It is still the case where the latest builds of the kernel breaks some mice. The buttons work, but no cursor movement. I've not been able to test this on F29 but I suspect it won't be fixed there either. Should this be considered a blocker? -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: system-config-date?
On 08/24/18 22:32, Robert Moskowitz wrote: > > > On 08/24/2018 10:16 AM, Ed Greshko wrote: >> On 08/24/18 21:44, Gerald Henriksen wrote: >>> On Thu, 23 Aug 2018 22:40:13 +0800, you wrote: >>> >>>> Anyway, were I to land in Helsinki today I would google "helsinki timezone" >>>> learn it >>>> is currently "summer time" there and it is GMT+3. So, I would do >>>> "timedatectl >>>> set-timezone Etc/GMT-3". I could not find a way to do that in the KDE >>>> GUI. Yet it >>>> does show up in the GUI after I set it in that manner. >>> Easiest way is right-click on the time in the task bar, Ajust Date and >>> Time, Time zones, and type in Helsinki. Benefit of this method is >>> essentaily the same process works on Windows or macOS so it is a >>> consistent method instead of hunting through system settings. >> That is one way. But it seemed to me that the OP was also concerned about >> landing in >> a city that didn't exist in the list and not knowing what city in the >> list was close to where he happens to be. >> >> My comment was to highlight that there seems to be no way in the KDE GUI to >> specify a >> GMT offset. >> >> Anyway, as the old saying goes, there is more ways than one to skin a >> cat...especially in linux. Considering my background and length of service I >> gravitate >> towards command lines than GUI if at all possible. > > And I earlier posted the tzupdate process that uses geolocation from your IP > address to set your timezone: > > pip install -U tzupdate > > But often this does not work with the IETF network as every meeting we have > the > same address block in a different country, and someone is not making the > geoloc > update. The NOC tries to get this done during setup, but they don't always > get the > cooperation from the host provider that they need. Thus we were in Singapore > with > the geoloc at first saying we were still in Prague. It was fixed by Tuesday > of the > meeting (or there abouts). > > I wonder how this would work with the airlines gogo wifi? :) Of course it won't work very well. If you're flying Delta your gateway address exposed to the world (assuming IPv4) would probably put you in Atlanta no matter where your plane is. All of this is why I just ask the hotel clerk: What time is it? OK, I also ask: Where am I? -- Conjecture is just a conclusion based on incomplete information. It isn't a fact. signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/UBQACG3IU5LVS27LKF53W6LEAHFIJ3VK/
