Re: Starting Wayland FC39

2023-11-19 Thread Dave Close
I wrote:

>Until FC39, I had only run Wayland on one of my machines, not even
>trying to bring it up on the others. Since I intensely dislike the
>graphic login, I found a way to start it from a virtual terminal like
>I normally start X11. Instead of "startx", I have a short script I
>call "startw" that contains only the single line,
>"/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I
>run KDE.) This worked on FC38.

>Now on the same machine with FC39 (upgraded with system-upgrade) this
>no longer works. Instead, it produces 248 lines of output and then
>terminates. Reviewing those lines, it appears that it is complaining
>about, 'failed to open drm device at "/dev/dri/card0"' and 'No
>suitable DRM devices have been found'.  I'm not sure what device
>that refers to but there seems to be some indication that it is my
>display. The display certainly works fine for the virtual terminal I
>use to run this script, and it also works fine for X11 if I run
>"startx".

>Ok, so as a fallback I tried a graphic login. This reaches a completely
>blank screen and goes no further. The machine is up as I can reach it
>with SSH but the display is useless. It responds to Ctrl-Alt-Delete
>but nothing else. I can't get it to switch to a different desktop. I
>noticed that SDDM defaults to Wayland so I changed "sddm.conf" to
>include "DisplayServer=x11". The allowed the graphic login to reach
>a login page but nothing I entered there was accepted even when I
>switched to specify starting an X11 session instead of Wayland.

>There are some online references to a problem with the /dev/dri/card0
>device but they are ancient and don't seem relevant.

>This machine is intended to run an application that only works on
>Wayland (Waydroid) so at this point I'm stimied. Any suggestions
>would be very helpful.

>If it matters, this machine was never installed with the KDE spin. It
>was installed before spins and with extensive editing of the packages to be
>included. KDE was added to it. It's been working through several Fedora
>releases for at least three years.

stan via users wrote:

>Have you tried creating a new user?  I'm wondering if there is some
>cruft in your configuration that a newer version of the executable is
>choking on. I don't see any bugzillas open against the package
>plasma-workspace that creates that rpm, so it doesn't seem to be a
>widespread problem.

I created a new user and obtained the same result using "startw".

I agree that this is not likely a plasma problem. It's the reference
to /dev/dri/card0 that concerns me. There must be some reason why this
device is needed but can't be found.

For what it may be worth, I'll attach the complete output (if that is
accepted on this list). Note that no other compositor is running as this
is immediately after a fresh reboot.
-- 
 Dave Close, Compata, Irvine CA   +1 714 434 7359
   d...@compata.com  dhcl...@alumni.caltech.edu
  "We consider too much the good luck of the early bird and
   not enough the bad luck of the early worm." -- Franklin Roosevelt

dbus-daemon[982960]: [session uid=1000 pid=982960] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=982961 
comm="/usr/bin/startplasma-wayland")
dbus-daemon[982960]: [session uid=1000 pid=982960] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
dbus-daemon[982960]: [session uid=1000 pid=982960] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=982961 
comm="/usr/bin/startplasma-wayland")
dbus-daemon[982960]: [session uid=1000 pid=982960] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
org.kde.plasma.libkworkspace: Skipping syncing of environment variable  
"BASH_FUNC_ml%%" as name contains unsupported characters
org.kde.plasma.libkworkspace: Skipping syncing of environment variable  
"BASH_FUNC_module%%" as name contains unsupported characters
dbus-daemon[982960]: [session uid=1000 pid=982960] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=982961 
comm="/usr/bin/startplasma-wayland")
dbus-daemon[982960]: [session uid=1000 pid=982960] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
org.kde.plasma.libkworkspace: Skipping syncing of environment variable  
"BASH_FUNC_ml%%" as name contains unsupported characters
org.kde.plasma.libkworkspace: Skipping syncing of environment variable  
"BASH_FUNC_module%%" as name contains unsupported characters
dbus-daemon[982960]: [session uid=1000 pid=982960] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=982961 
comm="/usr/bin/startplasma-wayland")
dbus-daemon[982960]: [session uid=1000 pid=982960] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1

Re: How to downgrade PHP

2023-11-19 Thread Clifford Snow
I'm actually using REMI. But that may be the solution - dropping REMI. Now
I need to see if REMI provides something needed by Nextcloud.

Thanks,
Clifford

On Sun, Nov 19, 2023 at 5:48 PM Todd Zullinger  wrote:

> Clifford Snow wrote:
> > I just upgraded my F39 machine and received PHP 8.3.0-RC6-1 - nice except
> > my Nextcloud installation doesn't like it. Any suggestions on how to
> > downgrade PHP to 8.2
>
> Fedora 39 has php-8.2.12-1.fc39.  If you're getting
> 8.3.0~RC6, you would appear to be on Rawhide (what will
> become Fedora 40 in about 6 months).
>
> --
> Todd
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


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


Re: How to downgrade PHP

2023-11-19 Thread Todd Zullinger
Clifford Snow wrote:
> I just upgraded my F39 machine and received PHP 8.3.0-RC6-1 - nice except
> my Nextcloud installation doesn't like it. Any suggestions on how to
> downgrade PHP to 8.2

Fedora 39 has php-8.2.12-1.fc39.  If you're getting
8.3.0~RC6, you would appear to be on Rawhide (what will
become Fedora 40 in about 6 months).

-- 
Todd


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


How to downgrade PHP

2023-11-19 Thread Clifford Snow
I just upgraded my F39 machine and received PHP 8.3.0-RC6-1 - nice except
my Nextcloud installation doesn't like it. Any suggestions on how to
downgrade PHP to 8.2

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


Re: adding static routes on fc38

2023-11-19 Thread Alex
Hi,

> I have a fedora38 server that's been updated to new versions many times
> over the years. It seems now I'm having a problem with the static route I
> created many years ago no longer being supported. I knew this was coming,
> but I'm unfamiliar with the new methods. I'm using the old network-tools
> method, not NM or even nmcli.
> >
> > It clearly doesn't understand my current config:
> > Nov 16 15:25:52 mail03 network[1123]: Bringing up interface enp0s31f6:
> > Nov 16 15:25:52 mail03 network[1313]: INFO  : [ipv6_wait_tentative]
> Waiting for interface enp0s31f6 IPv6 address(es) to leave the 'tentative'
> state
> > Nov 16 15:25:52 mail03 ipv6_wait_tentative: Waiting for interface
> enp0s31f6 IPv6 address(es) to leave the 'tentative' state
> > Nov 16 15:25:53 mail03 network[1313]: INFO  : [ipv6_wait_tentative]
> Waiting for interface enp0s31f6 IPv6 address(es) to leave the 'tentative'
> state
> > Nov 16 15:25:53 mail03 ipv6_wait_tentative: Waiting for interface
> enp0s31f6 IPv6 address(es) to leave the 'tentative' state
> > Nov 16 15:25:54 mail03 network[1370]: Error: either "to" is duplicate,
> or "gw" is a garbage.
> > Nov 16 15:25:54 mail03 network[1368]: WARN  :
> [/etc/sysconfig/network-scripts/ifup-routes] Failed to add route
> 192.168.1.0/24 gw 68.195.11.42 dev enp0s31f6, using ip route replace
> instead.
> > Nov 16 15:25:54 mail03 /etc/sysconfig/network-scripts/ifup-routes:
> Failed to add route 192.168.1.0/24 gw 68.195.11.42 dev enp0s31f6, using
> ip route replace instead.
> > Nov 16 15:25:54 mail03 network[1372]: Error: either "to" is duplicate,
> or "gw" is a garbage.
> > Nov 16 15:25:54 mail03 NET[1386]:
> /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
> > Nov 16 15:25:54 mail03 network[1123]: [  OK  ]
> >
> > In /etc/sysconfig/network-scripts/route-enp0s31f6 I have the following:
> > 192.168.1.0/24 gw 68.195.11.42 dev enp0s31f6
> >
> > In /etc/sysconfig/network-scripts/ifcfg-enp0s31f6 I have the following
> (my domain sanitized):
> > # cat ifcfg-enp0s31f6|grep -Ev '^$|^#'
> > HWADDR=4c:ed:fb:bb:47:93
> > BOOTPROTO=static
> > DEVICE=enp0s31f6
> > TYPE=Ethernet
> > ONBOOT=yes
> > IPADDR=68.195.11.45
> > GATEWAY=68.195.11.41
> > NETMASK=255.255.255.248
> > PREFIX=29
> > SEARCH="example.com"
> > DOMAIN="example.com"
> > DNS1=127.0.0.1
> > ZONE=FedoraServer
> > NM_CONTROLLED=no
> >
> > I'm also still using iptables, not firewalls or ipfw.
> >
> > Ideas on how to "upgrade" my server would be greatly appreciated.
>
> The first step you should do is to migrate the
> /etc/sysconfig/network-script to the NetworkManager standard configuration
> in /etc/NetworkManager. The /etc/sysconfig-method got deprecated some times
> ago and iwas withdrawn with F37 or so (don’t remember the exact release, it
> feels like it was s long ago). The network guys provided a nice
> migration tool which does all the work. Search the Fedora Magazine, there
> was an informative article about the migration process. (Just found it:
> https://fedoramagazine.org/converting-networkmanager-from-ifcfg-to-keyfiles/).
> The migration tool migrates the static routes, too.
>
> In case of difficulties, feel free to ask. Maybe on our Fedora Server
> mailing list.
>

This was a big help, thanks. The only thing it didn't do was migrate my
static route. I installed NetworkManager-tui and used the text interface to
add it manually. Now that I see what I did, I could probably do it again
manually.

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


Re: desktop power button

2023-11-19 Thread ToddAndMargo via users

On 11/17/23 21:28, ToddAndMargo via users wrote:
Create a .desktop file that runs "poweroff" or "reboot" depending on 
what you're wanting to do.


Thank you!

That will work perfectly.



I can easily work this into a bash script.

$ Xdialog --icon 
"/usr/share/icons/hicolor/48x48/actions/xfsm-shutdown.png" --wrap 
--title "Power Off" --yesno 'Power off?' 8 40; echo $?


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


Re: does Firefox honor local self-signed CAs ?

2023-11-19 Thread Barry
You have not said what you mean by sending that url.BarryOn 19 Nov 2023, at 17:49, Bryan  wrote:

  

  
  
http://www.cacert.org/

On 19/11/2023 17:37, Barry wrote:


  
  
  
  
On 19 Nov 2023, at 16:45, lejeczek via
  users  wrote:
  

  
  

  
  Hi guys

I put my own CAs certs into:
/etc/pki/ca-trust/source/anchors
then _update-ca-trust_
My other web-browsers seem happy but Firefox always
shows/warns: connection not secure
as oppose to other browsers saying: is secure
  
  
  
  
  You have to load your CA into Firefox itself. It does not fedora’s
  trust store.
  Search for certificate in Firefox settings.


Barry
  
 
Something has changed in default behavior - I remember
Firefox did not do it - even if it was possible to
"tweak" Firefox back to "normal"

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

  

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


  

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


Re: Python code error in F39, but not in F38

2023-11-19 Thread Neal Becker
Start gdb python.  Set a breakpoint in the shared module.  continue.

On Sun, Nov 19, 2023 at 1:02 PM Ranjan Maitra via users <
users@lists.fedoraproject.org> wrote:

> On Sun Nov19'23 05:35:19PM, Barry wrote:
> > From: Barry 
> > Date: Sun, 19 Nov 2023 17:35:19 +
> > To: Community support for Fedora users 
>  >
> > >
> > >
> > > It is possible that there is a bug in the code itself, but nothing
> above
> > > points to my created code.
> > >
> > > Any suggestions? Or is this a bug?
> >
> > Are you using C extensions in your code? If so I would suspect them for
> corrupting python. I think you can get into gdb inside the core file with
> coredumpctl debug.
>
> The python code calls a shared object library that is written in C. But
> why does this core dump only happen in F39 (python 3.12) and not with
> F38 (python 3.11)?
>
> > What does “info shared” tell you about what code has been loaded into
> memory?
>
> This would be under gdb, I presume.
>
>
> > It is also worth trying to find the type of the object that is being
> deleted, _PyObject_Free will have pointer to the object.
> > Also not sure where siplib.c is from is it python or an extension?
>
> Thanks, I don't know either, but there is no siplib.c anywhere on either
> of my two systems.
>
> > I am assuming here that you are familiar with debugging with gdb.
>
> Thanks, I am familiar with using gdb for a C program, never used it with
> python code calling a C shared object.
>
> I tried:
>
> $ gdb python "./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7"
> GNU gdb (Fedora Linux) 13.2-10.fc39
> Copyright (C) 2023 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from python...
>
> This GDB supports auto-downloading debuginfo from the following URLs:
>   
> Enable debuginfod for this session? (y or [n]) y
> Debuginfod has been enabled.
> To make this setting permanent, add 'set debuginfod enabled on' to
> .gdbinit.
> Reading symbols from
> /home/localuser/.cache/debuginfod_client/07023eb4f297ae1d4591e--Type 
> for more, q to quit, c to continue without paging--
> c808ab20b2788c542be/debuginfo...
> ./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7: No such file or
> directory.
> (gdb)
>
>
> Not quite sure how to proceed here.
>
> Many thanks again, and best wishes,
> Ranjan
>
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


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


Re: Python code error in F39, but not in F38

2023-11-19 Thread Ranjan Maitra via users
On Sun Nov19'23 05:35:19PM, Barry wrote:
> From: Barry 
> Date: Sun, 19 Nov 2023 17:35:19 +
> To: Community support for Fedora users 
 >
> >
> >
> > It is possible that there is a bug in the code itself, but nothing above
> > points to my created code.
> >
> > Any suggestions? Or is this a bug?
>
> Are you using C extensions in your code? If so I would suspect them for 
> corrupting python. I think you can get into gdb inside the core file with 
> coredumpctl debug.

The python code calls a shared object library that is written in C. But
why does this core dump only happen in F39 (python 3.12) and not with
F38 (python 3.11)?

> What does “info shared” tell you about what code has been loaded into memory?

This would be under gdb, I presume.


> It is also worth trying to find the type of the object that is being deleted, 
> _PyObject_Free will have pointer to the object.
> Also not sure where siplib.c is from is it python or an extension?

Thanks, I don't know either, but there is no siplib.c anywhere on either
of my two systems.

> I am assuming here that you are familiar with debugging with gdb.

Thanks, I am familiar with using gdb for a C program, never used it with
python code calling a C shared object.

I tried:

$ gdb python "./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7"
GNU gdb (Fedora Linux) 13.2-10.fc39
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from 
/home/localuser/.cache/debuginfod_client/07023eb4f297ae1d4591e--Type  for 
more, q to quit, c to continue without paging--
c808ab20b2788c542be/debuginfo...
./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7: No such file or directory.
(gdb)


Not quite sure how to proceed here.

Many thanks again, and best wishes,
Ranjan

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


Re: does Firefox honor local self-signed CAs ?

2023-11-19 Thread Barry


> On 19 Nov 2023, at 16:45, lejeczek via users  
> wrote:
> 
>  Hi guys
> 
> I put my own CAs certs into: /etc/pki/ca-trust/source/anchors
> then _update-ca-trust_
> My other web-browsers seem happy but Firefox always shows/warns: connection 
> not secure
> as oppose to other browsers saying: is secure

You have to load your CA into Firefox itself. It does not fedora’s trust store.
Search for certificate in Firefox settings.

Barry
> 
> Something has changed in default behavior - I remember Firefox did not do it 
> - even if it was possible to "tweak" Firefox back to "normal"
> 
> would you know?
> thanks, L.
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Python code error in F39, but not in F38

2023-11-19 Thread Barry


> On 19 Nov 2023, at 16:26, Ranjan Maitra via users 
>  wrote:
> 
> Hi,
> 
> I was running the code here: 
> https://github.com/maitra/Visual-Information-Fidelity---Python3
> 
> However, the code runs in F38 (python 3.11) without error, but not in F39 
> (python 3.12) where it
> ends with a segmentation fault (after doing the calculations).
> 
> Both, however, give an answer that are not the same after the 14th
> decimal place. Not sure if I should be bothered about that.
> 
> Looking at valgrind, I can not tell if there is an error in the python call 
> itself.  Here is what I get (note that the code calls shared objects created 
> by the gcc compiler).
> 
> ==278781== Invalid read of size 8
> ==278781==at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
> ==278781==by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
> ==278781==by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
> ==278781==by 0x6526E92E: UnknownInlinedFun (siplib.c:2241)
> ==278781==by 0x6526E92E: UnknownInlinedFun (objmap.c:69)
> ==278781==by 0x6526E92E: finalise (siplib.c:2143)
> ==278781==by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
> ==278781==by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
> ==278781==by 0x4B22336: Py_RunMain (main.c:691)
> ==278781==by 0x4ADD85B: Py_BytesMain (main.c:743)
> ==278781==by 0x4EE1149: (below main) (libc_start_call_main.h:58)
> ==278781==  Address 0x10 is not stack'd, malloc'd or (recently) free'd
> ==278781==
> ==278781==
> ==278781== Process terminating with default action of signal 11 (SIGSEGV): 
> dumping core
> ==278781==  Access not within mapped region at address 0x10
> ==278781==at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
> ==278781==by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
> ==278781==by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
> ==278781==by 0x6526E92E: finalise (siplib.c:2143)
> ==278781==by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
> ==278781==by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
> ==278781==by 0x4B22336: Py_RunMain (main.c:691)
> ==278781==by 0x4ADD85B: Py_BytesMain (main.c:743)
> ==278781==by 0x4EE1149: (below main) (libc_start_call_main.h:58)
> ==278781==  If you believe this happened as a result of a stack
> ==278781==  overflow in your program's main thread (unlikely but
> ==278781==  possible), you can try to increase the size of the
> ==278781==  main thread stack using the --main-stacksize= flag.
> ==278781==  The main thread stack size used in this run was 8388608.
> ==278781==
> ==278781== HEAP SUMMARY:
> ==278781== in use at exit: 18,046,811 bytes in 92,137 blocks
> ==278781==   total heap usage: 2,212,074 allocs, 2,119,937 frees, 
> 1,983,813,202 bytes allocated
> ==278781==
> ==278781== LEAK SUMMARY:
> ==278781==definitely lost: 2,160,027 bytes in 41,915 blocks
> ==278781==indirectly lost: 112 bytes in 2 blocks
> ==278781==  possibly lost: 5,021,632 bytes in 34,430 blocks
> ==278781==still reachable: 10,863,024 bytes in 15,769 blocks
> ==278781== suppressed: 0 bytes in 0 blocks
> 
> 
> 
> It is possible that there is a bug in the code itself, but nothing above
> points to my created code.
> 
> Any suggestions? Or is this a bug?

Are you using C extensions in your code? If so I would suspect them for 
corrupting python. I think you can get into gdb inside the core file with 
coredumpctl debug.
What does “info shared” tell you about what code has been loaded into memory?
It is also worth trying to find the type of the object that is being deleted, 
_PyObject_Free will have pointer to the object.
Also not sure where siplib.c is from is it python or an extension?

I am assuming here that you are familiar with debugging with gdb.

Barry

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


does Firefox honor local self-signed CAs ?

2023-11-19 Thread lejeczek via users

Hi guys

I put my own CAs certs into: /etc/pki/ca-trust/source/anchors
then _update-ca-trust_
My other web-browsers seem happy but Firefox always 
shows/warns: connection not secure

as oppose to other browsers saying: is secure

Something has changed in default behavior - I remember 
Firefox did not do it - even if it was possible to "tweak" 
Firefox back to "normal"


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


Python code error in F39, but not in F38

2023-11-19 Thread Ranjan Maitra via users
Hi,

I was running the code here: 
https://github.com/maitra/Visual-Information-Fidelity---Python3

However, the code runs in F38 (python 3.11) without error, but not in F39 
(python 3.12) where it
ends with a segmentation fault (after doing the calculations).

Both, however, give an answer that are not the same after the 14th
decimal place. Not sure if I should be bothered about that.

Looking at valgrind, I can not tell if there is an error in the python call 
itself.  Here is what I get (note that the code calls shared objects created by 
the gcc compiler).

==278781== Invalid read of size 8
==278781==at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
==278781==by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
==278781==by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
==278781==by 0x6526E92E: UnknownInlinedFun (siplib.c:2241)
==278781==by 0x6526E92E: UnknownInlinedFun (objmap.c:69)
==278781==by 0x6526E92E: finalise (siplib.c:2143)
==278781==by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
==278781==by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
==278781==by 0x4B22336: Py_RunMain (main.c:691)
==278781==by 0x4ADD85B: Py_BytesMain (main.c:743)
==278781==by 0x4EE1149: (below main) (libc_start_call_main.h:58)
==278781==  Address 0x10 is not stack'd, malloc'd or (recently) free'd
==278781==
==278781==
==278781== Process terminating with default action of signal 11 (SIGSEGV): 
dumping core
==278781==  Access not within mapped region at address 0x10
==278781==at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
==278781==by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
==278781==by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
==278781==by 0x6526E92E: finalise (siplib.c:2143)
==278781==by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
==278781==by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
==278781==by 0x4B22336: Py_RunMain (main.c:691)
==278781==by 0x4ADD85B: Py_BytesMain (main.c:743)
==278781==by 0x4EE1149: (below main) (libc_start_call_main.h:58)
==278781==  If you believe this happened as a result of a stack
==278781==  overflow in your program's main thread (unlikely but
==278781==  possible), you can try to increase the size of the
==278781==  main thread stack using the --main-stacksize= flag.
==278781==  The main thread stack size used in this run was 8388608.
==278781==
==278781== HEAP SUMMARY:
==278781== in use at exit: 18,046,811 bytes in 92,137 blocks
==278781==   total heap usage: 2,212,074 allocs, 2,119,937 frees, 1,983,813,202 
bytes allocated
==278781==
==278781== LEAK SUMMARY:
==278781==definitely lost: 2,160,027 bytes in 41,915 blocks
==278781==indirectly lost: 112 bytes in 2 blocks
==278781==  possibly lost: 5,021,632 bytes in 34,430 blocks
==278781==still reachable: 10,863,024 bytes in 15,769 blocks
==278781== suppressed: 0 bytes in 0 blocks



It is possible that there is a bug in the code itself, but nothing above
points to my created code.

Any suggestions? Or is this a bug?

Many thanks and best wishes,
Ranjan

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


Re: Problem Reporting.

2023-11-19 Thread Barry Scott


> On 19 Nov 2023, at 15:15, Ger van Dijck  wrote:
> 
> Hay All,
> 
> 
> When I want to send a problem to Fedora I get the message 
> https://retrace.fedoraproject.org  Error 404 .
> 
> 
> So I have to change the URL .
> 
> 
> 
> What is the new name ?

Have you setup a bugzilla account to config ABRT with?
Without that account it cannot raise the bug on your behalf.
I forget how to set this up. I'm guessing that saw prompts in
UI that told be what was expected.

Barry

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


Re: zbar VS qrencode

2023-11-19 Thread Barry Scott


> On 19 Nov 2023, at 14:29, lejeczek via users  
> wrote:
> 
> Would anybody know if _zbarimg_ is looked after still, if it's worth filing a 
> bug?

The internet knows!

A web search and click or two got me here 
https://sourceforge.net/p/zbar/code/commit_browser
The last commit was in 2012.

Barry

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


Problem Reporting.

2023-11-19 Thread Ger van Dijck

Hay All,


When I want to send a problem to Fedora I get the message 
https://retrace.fedoraproject.org  Error 404 .



So I have to change the URL .



What is the new name ?




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


Re: Starting Wayland FC39

2023-11-19 Thread stan via users
On Fri, 17 Nov 2023 19:44:49 -0800
Dave Close  wrote:

> I wrote:
> 
> >Until FC39, I had only run Wayland on one of my machines, not even
> >trying to bring it up on the others. Since I intensely dislike the
> >graphic login, I found a way to start it from a virtual terminal like
> >I normally start X11. Instead of "startx", I have a short script I
> >call "startw" that contains only the single line,
> >"/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I
> >run KDE.) This worked on FC38.
> >
> >Now on the same machine with FC39 (upgraded with system-upgrade) this
> >no longer works. Instead, it produces 248 lines of output and then
> >terminates. Reviewing those lines, it appears that it is complaining
> >about, 'failed to open drm device at "/dev/dri/card0"' and 'No
> >suitable DRM devices have been found'.  I'm not sure what device
> >that refers to but there seems to be some indication that it is my
> >display. The display certainly works fine for the virtual terminal I
> >use to run this script, and it also works fine for X11 if I run
> >"startx".

Have you tried creating a new user?  I'm wondering if there is some
cruft in your configuration that a newer version of the executable is
choking on. I don't see any bugzillas open against the package
plasma-workspace that creates that rpm, so it doesn't seem to be a
widespread problem.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: zbar VS qrencode

2023-11-19 Thread lejeczek via users



On 19/11/2023 14:17, lejeczek via users wrote:

Hi guys

I have a peculiar case, I think, while using national chars.
I wonder which one is _playing_ up here, qrencode or zbarimg

When I with:
-> qrencode -l L -v 1 ..
encode:

ADR;LABEL="Kukólka":;;;Kukólka;Mazowieckie;PL
then:

-> $ zbarimg ...
...
ADR;LABEL="Kuk籀lka":;;;Kuk籀lka;Mazowieckie;PL

but when I encode:
ADR;LABEL="Kukółka":;;;Kukółka;Mazowieckie;PL
then:

-> $ zbarimg 
...
ADR;LABEL="Kukółka":;;;Kukółka;Mazowieckie;PL

you see - if all the "processors" between our email 
clients, mine your yours, did not mangle the content - it 
seems when there is only *single* polish char - ó - then 
_zbaring_ shows that weird output - a Korean or Japanese?
Any other case, add just one morenational char in the line 
and the output, even that same - ó - mangled when single, 
now shows as it should.
So I checked all nine polish national chars and it's: ó 
and ż when occur as single in a line - _zbarimg_ shows 
them incorrectly. (or _qrencode_ fails?)


Any _qrencode_ & _zbarimg_ users here who use their 
national chars?

I'll be glad for all comments.

thanks, L.


Ah, to answer my question - partly at least - seems that 
_zbarimg_ could use some fixing up.

Trying _qrscanner_ and here I get everything shown correctly.

Would anybody know if _zbarimg_ is looked after still, if 
it's worth filing a bug?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


zbar VS qrencode

2023-11-19 Thread lejeczek via users

Hi guys

I have a peculiar case, I think, while using national chars.
I wonder which one is _playing_ up here, qrencode or zbarimg

When I with:
-> qrencode -l L -v 1 ..
encode:

ADR;LABEL="Kukólka":;;;Kukólka;Mazowieckie;PL
then:

-> $ zbarimg ...
...
ADR;LABEL="Kuk籀lka":;;;Kuk籀lka;Mazowieckie;PL

but when I encode:
ADR;LABEL="Kukółka":;;;Kukółka;Mazowieckie;PL
then:

-> $ zbarimg 
...
ADR;LABEL="Kukółka":;;;Kukółka;Mazowieckie;PL

you see - if all the "processors" between our email clients, 
mine your yours, did not mangle the content - it seems when 
there is only *single* polish char - ó - then _zbaring_ 
shows that weird output - a Korean or Japanese?
Any other case, add just one morenational char in the line 
and the output, even that same - ó - mangled when single, 
now shows as it should.
So I checked all nine polish national chars and it's: ó and 
ż when occur as single in a line - _zbarimg_ shows them 
incorrectly. (or _qrencode_ fails?)


Any _qrencode_ & _zbarimg_ users here who use their national 
chars?

I'll be glad for all comments.

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


Re: DNF Upgrade from F38 to F39 Issues

2023-11-19 Thread John Pilkington

On 19/11/2023 07:29, Tim via users wrote:

Jeffrey Walton wrote:

* SecureBoot should be turned off if using tainted kernel drivers. Or,
you can cutover to driver signing. I usually turn off SecureBoot
because I don't like messing around with driver signing. In my case,
it usually is due to VirtualBox, not NVIDIA.


Stephen Morris:

As my system is a tri-boot between Windows 11, Fedora 39 and Ubuntu
22.04, and Windows doesn't seem to work properly with UEFI disabled,
I've gone down the path of signing the nvidia drivers under Fedora and
Ubuntu, using separate passwords as I found using the same password
causes thing to not work properly.



UEFI is a hardware interface (simplifying that description quite a lot)
between the PC's hardware, firmware, and the OS before it boots, and
the control screens it gives you for you to configure things.  It's an
update on the similiar, but more primitive, thing done with the old
BIOS.

Secure boot is a *separate* thing (though probably only exists on
systems with UEFI).  It's to do with only booting up from signed
binaries (to verify that only authentic things can run, blocking any
fake things that have snuck in).

A problem with Secure Boot is that there are real and genuine things
you may want to use that are not signed (such as some graphics card
drivers).  One solution to that is to sign them yourself, with a
signature that you let things know that *you* trust.

("Signed" in these contexts is to do with cryptographic keys.)

Though again, it could be that Windows won't boot without secure boot
options set, not UEFI being disabled (not that I've seen a motherboard
where you could disable UEFI and go back to BIOS).  That and the TPM
hardware that's touted as being more fantastic than it really is.

As a home user you may feel that this security is kinda pointless, as
no-one else is going to touch your PC and sneak things in.  And
anything nasty that does get in is going to get in by your own
behaviour doing unwise things, for which you're going to ignore and
disable any warnings not to do it.  To that degree, that's true.  And
the same can be said about AntiVirus, SELinux, file permissions and
ownership.  But where such security features can help, is when you
start to do something unwise without realising it, it blocks you, and
you properly investigate the reasons.


In https://bugzilla.redhat.com/show_bug.cgi?id=2011120 I reported seeing 
this problem on one system, but not on another.  The one with the 
problem, solved by reinstalling the rpmfusion 470xx packages. has dual 
boot with Windows 10 - but the selection is made via the HP BIOS 
immediately after power-up;  the default is Windows, but if 'escaped' in 
the first few seconds it offers other options, including UEFI boots of 
Windows and Fedora.  Choosing Fedora gives the normal grub screen.


It's inconvenient but it works and I haven't tried changing it 'for fear 
of finding something worse'.  Maybe I should add this info to the BZ. 
Might it explain the different behaviour on Fedora version upgrade?


John P



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