I've just upgraded from F34 to F35 and have troubles with KDE vs
Wayland and X11.
Wayland is very flaky, crashes of various kinds, sometimes killing
individual apps, sometimes an entire session. I can't reproduce the
crashes reliably; they happen when they happen. The only thing that may
be relevant is that I am running Firefox with many (probably too many)
windows and tabs.
X11 messes up konsole, the KDE terminal emulator. When typing onto the
screen, not displaying text generated by an application, the test
appears slowly and with many strange artifacts. It looks like the text
appears on one interlace and then gradually gets better; the text takes
about 500 msec to recover; the same thing happens with window
decorations when I mouse over them. I have attempted to record screen
behavior using simplescreenrecorder, but when I start it, the problem
Right now I'm using X11 with gnome-terminal, which doesn't show the
Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.12-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600
All Suggestions Welcome - Jonathan Ryshpan <jonrysh(a)pacbell.net>
What is love? 'tis not hereafter;
Present mirth hath present laughter.
What's to come is still unsure:
In delay there lies no plenty,
Then come kiss me, sweet and twenty.
Youth's a stuff will not endure."
-- Shakespeare's Twelfth Night
We would love to have people play with this and test it out.
Note: this release has breaking changes to it's API, so it will not be
released to f35. Only to F36, but users will be able to download and use
it on F35, we will not push it to stable though.
I have a 43" Samsung Smart TV that I am using as a monitor with a ThinkPad P51, running Fedora 35 Workstation Edition. This laptop has a "NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] / Mesa Intel® HD Graphics 630 (KBL GT2)" graphics subsystem. As far as I can make out, I am using the latest NVidia driver (495.46).
What is unfortunately happening, is that if my laptop goes to sleep, the TV sees that the source disappears, and "tries to look for the laptop", repeatedly. This ends up waking up the laptop (sometimes), until the TV eventually gives up and turns itself off. The problem is then that the laptop no longer detects that the TV is connected to the HDMI port, and I have to reboot to allow the laptop to detect the screen again. Xrandr does not detect the display if run manually, and the Settings app Displays page also doesn't show the TV.
This is a rather difficult thing to google, I have had zero results in my searching.
I also tried looking for any logs that would indicate what went wrong, but I found nothing in the syslog, etc.
Can anyone give me pointers on how I can start debugging this? I am fairly technical, so can certainly follow instructions. I'm guessing I need to enable verbose logging for the driver so it can report when new displays are connected or disconnected, as well as any actions around those events?
When I run octave with
pkg load symbolic
Symbolic pkg v2.9.0: Traceback (most recent call last):
File "<stdin>", line 28, in <module>
AttributeError: '_PrintFunction' object has no attribute '__globals__'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 12, in octoutput_drv
File "<stdin>", line 54, in octoutput
File "<stdin>", line 55, in octoutput
AttributeError: module 'sympy' has no attribute 'compatibility'
Closing the Python communications link.
error: Python exception: AttributeError: '_PrintFunction' object has no attribute '__globals__'
occurred in python_header import block.
Try "sympref reset" and repeat your command?
(consider filing an issue at https://github.com/cbm755/octsympy/issues)
error: called from
pycall_sympy__ at line 191 column 5
valid_sym_assumptions at line 38 column 10
assumptions at line 82 column 7
syms at line 97 column 13
It seems that it is an identified bug, due to sympy
This is really more than annoying.
if we cannot use the symbolic package with octave
Do you more about the future of this packages?
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
On Jan 22, 2022, at 06:35, Dorian ROSSE <dorianbrice(a)hotmail.fr> wrote:
> Have you tried 'pip3 install python3dist ' ?
I never suggest Fedora users run ‘pip’ as root, except when in a virtualenv, dockerfile or some contained environment.
It is far too easy for pip to overwrite or override a packaged python library and break system tools, such as the ones used in DNF. Once you’ve broken dnf, it is hard to fix those libraries since dnf is the tool to fix them.
On Jan 23, 2022, at 08:17, Dorian ROSSE <dorianbrice(a)hotmail.fr> wrote:
> Every time I miss a program python because I use the most Ubuntu instead fedora I use 'pip3 install theprogrampython '
> But I don't understand how to become more tough dnf,
Well, you are doing it in a way that will break your OS, eventually. It’s not a question of DNF becoming “tougher”. You are suggesting people use two different package managers, simultaneously, and neither knows about the other.
Imagine hiring two builders to install a new furnace in a house, and not telling them about the other. You’d end up with two confused builders and a broken furnace.
If you want to use pip as root and can’t be bothered to use virtual environments, install python outside of DNF, either from source into /usr/local or /opt, or use something like “conda”, which has its own prefix. Then, at least if it breaks something, it won’t prevent you from updating your OS.
FWIW, in Centos 8 stream, DNF uses a python that isn’t installed as /usr/bin/python so it is less likely for ignorant people to break, although I’ve discovered that Ansible *does* find it and will happy install python modules in it and break things.
I've got an odd problem that I was hoping for some help on.
The laptop was previously working fine, I am running F30, updated regularly.
I've got an Acer laptop that has been shutting down suddenly. (I
suspect a bad battery, working on that.)
After a sudden shutdown last night, I now get a kernel panic on boot
right after "Starting Switch Root..."
I was able to boot from a USB stick, and was able to read the journal,
but I didn't see anything obvious to help.
I was able to get all of my data off of the (encrypted) disks, so
that's not a problem, but I don't want to just give up, and wash and
reload too quickly.
On Sun, 2022-01-23 at 11:24 +0000, Dorian ROSSE wrote:
> dnf has need to become tough because pip and pip3 are the packager
> the most used by all import,
Little sir echo how do you do?
Linux 3.10.0-1160.53.1.el7.x86_64 #1 SMP Fri Jan 14 13:59:45 UTC 2022 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.