Re: [CentOS] C8: Wayland Session / Cut and Paste
On 2019-11-07 3:13 p.m., Leon Fauster via CentOS wrote: > Is this the normal behavior now? Cutting text in gedit and pasting it > into the terminal needs that the source application stays running? I don't know if it's related, but I ran into a problem when highlight -> middle-click to paste stopped working in kate on Fedora 31 on Wayland. Worked fine on Fedora 30, and works on F31 + Xorg. So it's a Wayland issue of some sort. https://bugzilla.redhat.com/show_bug.cgi?id=1770057 -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8: Wayland Session / Cut and Paste
On Thu, Nov 07, 2019 at 05:50:24PM -0500, Lamar Owen wrote: > On 11/7/19 3:13 PM, Leon Fauster via CentOS wrote: > >Is this the normal behavior now? Cutting text in gedit and pasting > >it into the terminal needs that the source application stays > >running? > I've run into this behavior for a while, for several CentOS > versions, depending upon the application. there are also (at least in X) two ways to cut and paste: 1. select with mouse then paste with middle-click. 2. select with mouse, right-click "select", paste the right-click "paste". My understanding is that oneuses X facilities and the other is part of the desktop. I would surmise that Weston could be different. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The Lord is like a strong tower. Those who do what is right can run to him for safety. --- Proverbs 18:10 (niv) - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8: Wayland Session / Cut and Paste
On 11/7/19 3:13 PM, Leon Fauster via CentOS wrote: Is this the normal behavior now? Cutting text in gedit and pasting it into the terminal needs that the source application stays running? I've run into this behavior for a while, for several CentOS versions, depending upon the application. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8: Wayland Session / Cut and Paste
I am going to check on that as well because I'm using Fedora 31/wayland as desktop and I experienced the same behavior On Thu, Nov 7, 2019, 3:13 PM Leon Fauster via CentOS wrote: > Is this the normal behavior now? Cutting text in gedit and pasting it > into the terminal needs that the source application stays running? > > -- > Leon > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8: Wayland Session / Cut and Paste
Is this the normal behavior now? Cutting text in gedit and pasting it into the terminal needs that the source application stays running? -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible Font problem with CentOS 7
On Wed, 2019-11-06 at 20:19 +, liam.p.oto...@gmail.com wrote: > CAUTION: This email originated from outside of the University of > Limerick. Do not click on links or open attachments unless you > recognize the sender's email address and know the content is safe. > On Wed, 06 Nov, 2019 at 19:45:22 +, Tony Molloy wrote: > > > > Hi, > > > > I've got a possible font problem with a fully updated CentOS 7 > > system. > > > > An example with the man command. > > > > #man kill > > > > Should return the following > > > > KILL(1) User Commands KILL(1) > > > > NAME > >kill - terminate a process > > > > SYNOPSIS > >kill [-s signal|-p] [-q sigval] [-a] [--] pid... > >kill -l [signal] > > > > > > but what I actually get is the following > > > > KILL(1) User CommandsKILL(1) > > > > > >kill - terminate a process > > > > > > [ signal| ] [ sigval] [ ] [ ] pid... > > [signal] > > > > Notice the missing text. > > > > If I select the text and paste it into an editor I see the missing > > text. So it's there just not displaying on the screen. > > > > I also notice the effect with links embedded in e-mails. I use > > evolution. Embedded links do not appear in the e-mail but if I > > hover > > over a link location then it appears in the text box at the bottom > > of > > the page and I can select it. > > > > I suspect I'm missing some common font(s). > > > > Any ideas. > > > > Regards, > > > > Tony > > Greetings from Cork. > > What terminal emulator are you using? Assuming it's gnome-terminal > (the default), what > is the output of the commands > > gsettings get org.gnome.desktop.interface monospace-font-name > 'Monospace 11' > and > > fc-match monospace > DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" I got the solution for the terminal problem. It was a setting in the terminal preferences settings which I had unticked. So now for the e-mail problem. This I assume is also a preferences problem with either my theme selection or with evoloution itself. Thanks for the reply, Tony -- Tony Molloy Home ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible Font problem with CentOS 7
On Wed, 2019-11-06 at 13:57 -0600, > This is caused by the colour profile settings in your terminal > program (gnome-terminal, mate-terminal, whatever). > > Edit-Prefrences-Colors > > I generally just check "use colors from system theme" but I suppose > that would depend on what you're using for a system theme. But the > setting you need to fix is under Text and Background Color. > Thanks, that sorted the terminal problem. Now for the e-mail problem. Regards, Tony > On Wed, 06 Nov 2019 19:45:22 + > Tony Molloy wrote: > > > > > Hi, > > > > I've got a possible font problem with a fully updated CentOS 7 > > system. > > > > An example with the man command. > > > > #man kill > > > > Should return the following > > > > KILL(1) User Commands KILL(1) > > > > NAME > >kill - terminate a process > > > > SYNOPSIS > >kill [-s signal|-p] [-q sigval] [-a] [--] pid... > >kill -l [signal] > > > > > > but what I actually get is the following > > > > KILL(1) User CommandsKILL(1) > > > > > >kill - terminate a process > > > > > > [ signal| ] [ sigval] [ ] [ ] pid... > > [signal] > > > > Notice the missing text. > > > > If I select the text and paste it into an editor I see the missing > > text. So it's there just not displaying on the screen. > > > > I also notice the effect with links embedded in e-mails. I use > > evolution. Embedded links do not appear in the e-mail but if I > > hover > > over a link location then it appears in the text box at the bottom > > of > > the page and I can select it. > > > > I suspect I'm missing some common font(s). > > > > Any ideas. > > > > Regards, > > > > Tony > > > > > > > > > > > > > > -- > > Tony Molloy > > Home > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > -- Tony Molloy Home ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] printer only prints one page, if anything
On Thu, 7 Nov 2019, Pete Biggs wrote: [Michael Hennebry] 'Tain't as big a deal as having none, but why does CUPS have two queue names for the printer? Do you have CUPS autodiscover turned on? (AKA Avahi on Linux systems), if so CUPS will have automatically added the printer in addition to the one you manually added. Ah. That makes sense. I think they were the same packages that I tried to use. In any case, they both ended in 386. Once again, do you have a 64 bit system? If so, then any executables in the RPMs won't work unless you have added the 32-bit compatibility stuff. RPMs aren't magic, they need to have the requirements added by the packager and if the requirements aren't mentioned in the RPM, it will still install, but none of the executables will run. They will come up with Bad ELF errors. It must have found whatever it needed: Both queues work. system-config-printer is the old way of adding and managing printers. It's a GUI, but you can start it from a command line in a GUI environment (i.e. it's not a command line program). But it's just a front end, you still need the underlying drivers there before it can configure a printer. Add printer worked after I added myself to the lp and sys groups. The cups_error file gave me something to search for. All good now. -- Michael henne...@web.cs.ndsu.nodak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8.1 build status
Am 07.11.19 um 17:40 schrieb Strahil via CentOS: Hi Community, Does anyone got info on 8.1 build status ? The following URL is outdated: https://wiki.centos.org/About/Building_8 ... as usual there is a delta between upstream and CentOS. After two days I would guess; status => at the beginning. -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 8.1 build status
Hi Community, Does anyone got info on 8.1 build status ? The following URL is outdated: https://wiki.centos.org/About/Building_8 Best Regards, Strahil Nikolov ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum install fails - itertoolsmodule.so
Hi Paddy, I was suspecting the same, and from the output below I think you're right. However, I was hoping I could just repair this problem for now, and worry about replacing the HDD later. I need to resume some services that also seem to generate this same error. Gary [root@zeppo services]# ll /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so -rwxr-xr-x. 1 root root 61976 Sep 15 2016 /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so [root@zeppo services]# cat /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so cat: /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so: Input/output error [root@zeppo services]# On Thursday 07 November 2019 16:25:54 Paddy Doyle wrote: > Hi Gary, > > That "Input/output error" suggests a disk problem to me. Does that file > /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so actually exist and is > it readable? > > Also look the the output of 'rpm -V python-libs' to see if rpm considers > the installed files to be corrupt. > > If it's not that, then you could try 'yum reinstall python-libs'. > > Paddy > > On Thu, Nov 07, 2019 at 04:18:18PM +, Gary Stainburn wrote: > > > I've just tried a yum update on one of my C7 boxes and got the following > > output. > > > > I'm guessing to fix this I need to re-install the RPM, but I can't remove > > it because of dependancies, so how can I fix the problem? > > I've managed to download a later version of the RPM, but haven't managed to > > find the same version as the one installed. > > > > Gary > > > > [root@zeppo ~]# yum install > > There was a problem importing one of the Python modules > > required to run yum. The error leading to this problem was: > > > >/usr/lib64/python2.7/lib-dynload/itertoolsmodule.so: cannot read file > > data: Input/output error > > > > Please install a package which provides this module, or > > verify that the module is installed correctly. > > > > It's possible that the above module doesn't match the > > current version of Python, which is: > > 2.7.5 (default, Sep 15 2016, 22:37:39) > > [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] > > > > If you cannot solve this problem yourself, please go to > > the yum faq at: > > http://yum.baseurl.org/wiki/Faq > > > > > > [root@zeppo ~]# rpm -qf /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so > > python-libs-2.7.5-39.el7_2.x86_64 > > [root@zeppo ~]# > > [root@zeppo ~]# rpm -e python-libs-2.7.5-39.el7_2.x86_64 > > error: Failed dependencies: > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-lxml-3.2.1-4.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > yum-metadata-parser-1.1.4-10.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > pyliblzma-0.5.3-11.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > pyxattr-0.5.1-5.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > cmpi-bindings-pywbem-0.9.5-6.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-kmod-0.9-4.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > newt-python-0.52.15-4.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-setproctitle-1.1.6-5.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-ethtool-0.8-5.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-urwid-1.1.1-3.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-pycurl-7.19.0-17.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > PyYAML-3.10-11.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > pygpgme-0.3-9.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-cups-1.9.63-6.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-2.7.5-39.el7_2.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > libxml2-python-2.9.1-6.el7_2.3.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > gdb-7.6.1-80.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-dmidecode-3.10.13-11.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-perf-3.10.0-327.36.3.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > cryptsetup-python-1.6.7-1.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > pyparted-1:3.9-13.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > rpm-python-4.11.3-17.el7.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > iscsi-initiator-utils-6.2.0.873-33.el7_2.2.x86_64 > > libpython2.7.so.1.0()(64bit) is needed by (installed) > > python-pcp-3.10.6-2.el7.x86_64 > >
Re: [CentOS] yum install fails - itertoolsmodule.so
Hi Gary, That "Input/output error" suggests a disk problem to me. Does that file /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so actually exist and is it readable? Also look the the output of 'rpm -V python-libs' to see if rpm considers the installed files to be corrupt. If it's not that, then you could try 'yum reinstall python-libs'. Paddy On Thu, Nov 07, 2019 at 04:18:18PM +, Gary Stainburn wrote: > I've just tried a yum update on one of my C7 boxes and got the following > output. > > I'm guessing to fix this I need to re-install the RPM, but I can't remove it > because of dependancies, so how can I fix the problem? > I've managed to download a later version of the RPM, but haven't managed to > find the same version as the one installed. > > Gary > > [root@zeppo ~]# yum install > There was a problem importing one of the Python modules > required to run yum. The error leading to this problem was: > >/usr/lib64/python2.7/lib-dynload/itertoolsmodule.so: cannot read file > data: Input/output error > > Please install a package which provides this module, or > verify that the module is installed correctly. > > It's possible that the above module doesn't match the > current version of Python, which is: > 2.7.5 (default, Sep 15 2016, 22:37:39) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] > > If you cannot solve this problem yourself, please go to > the yum faq at: > http://yum.baseurl.org/wiki/Faq > > > [root@zeppo ~]# rpm -qf /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so > python-libs-2.7.5-39.el7_2.x86_64 > [root@zeppo ~]# > [root@zeppo ~]# rpm -e python-libs-2.7.5-39.el7_2.x86_64 > error: Failed dependencies: > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-lxml-3.2.1-4.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > yum-metadata-parser-1.1.4-10.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > pyliblzma-0.5.3-11.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > pyxattr-0.5.1-5.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > cmpi-bindings-pywbem-0.9.5-6.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-kmod-0.9-4.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > newt-python-0.52.15-4.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-setproctitle-1.1.6-5.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-ethtool-0.8-5.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-urwid-1.1.1-3.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-pycurl-7.19.0-17.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > PyYAML-3.10-11.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > pygpgme-0.3-9.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-cups-1.9.63-6.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-2.7.5-39.el7_2.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > libxml2-python-2.9.1-6.el7_2.3.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > gdb-7.6.1-80.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-dmidecode-3.10.13-11.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-perf-3.10.0-327.36.3.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > cryptsetup-python-1.6.7-1.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > pyparted-1:3.9-13.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > rpm-python-4.11.3-17.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > iscsi-initiator-utils-6.2.0.873-33.el7_2.2.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-pcp-3.10.6-2.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > lvm2-python-libs-7:2.02.130-5.el7_2.5.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > perf-3.10.0-327.36.3.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > m2crypto-0.21.1-17.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > python-pillow-2.0.0-19.gitd1c6db8.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > bacula-libs-5.2.13-23.1.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > bacula-storage-5.2.13-23.1.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > bacula-client-5.2.13-23.1.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) > gnome-python2-canvas-2.28.1-14.el7.x86_64 > libpython2.7.so.1.0()(64bit) is needed by (installed) >
[CentOS] yum install fails - itertoolsmodule.so
I've just tried a yum update on one of my C7 boxes and got the following output. I'm guessing to fix this I need to re-install the RPM, but I can't remove it because of dependancies, so how can I fix the problem? I've managed to download a later version of the RPM, but haven't managed to find the same version as the one installed. Gary [root@zeppo ~]# yum install There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so: cannot read file data: Input/output error Please install a package which provides this module, or verify that the module is installed correctly. It's possible that the above module doesn't match the current version of Python, which is: 2.7.5 (default, Sep 15 2016, 22:37:39) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] If you cannot solve this problem yourself, please go to the yum faq at: http://yum.baseurl.org/wiki/Faq [root@zeppo ~]# rpm -qf /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so python-libs-2.7.5-39.el7_2.x86_64 [root@zeppo ~]# [root@zeppo ~]# rpm -e python-libs-2.7.5-39.el7_2.x86_64 error: Failed dependencies: libpython2.7.so.1.0()(64bit) is needed by (installed) python-lxml-3.2.1-4.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) yum-metadata-parser-1.1.4-10.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) pyliblzma-0.5.3-11.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) pyxattr-0.5.1-5.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) cmpi-bindings-pywbem-0.9.5-6.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-kmod-0.9-4.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) newt-python-0.52.15-4.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-setproctitle-1.1.6-5.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-ethtool-0.8-5.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-urwid-1.1.1-3.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-pycurl-7.19.0-17.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) PyYAML-3.10-11.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) pygpgme-0.3-9.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-cups-1.9.63-6.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-2.7.5-39.el7_2.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) libxml2-python-2.9.1-6.el7_2.3.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) gdb-7.6.1-80.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-dmidecode-3.10.13-11.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-perf-3.10.0-327.36.3.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) cryptsetup-python-1.6.7-1.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) pyparted-1:3.9-13.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) rpm-python-4.11.3-17.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) iscsi-initiator-utils-6.2.0.873-33.el7_2.2.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-pcp-3.10.6-2.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) lvm2-python-libs-7:2.02.130-5.el7_2.5.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) perf-3.10.0-327.36.3.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) m2crypto-0.21.1-17.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) python-pillow-2.0.0-19.gitd1c6db8.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) bacula-libs-5.2.13-23.1.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) bacula-storage-5.2.13-23.1.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) bacula-client-5.2.13-23.1.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) gnome-python2-canvas-2.28.1-14.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) gnome-python2-bonobo-2.28.1-14.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) gnome-python2-gnomevfs-2.28.1-14.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) gnome-python2-gnome-2.28.1-14.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) pytalloc-2.1.6-1.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) samba-libs-0:4.4.4-9.el7.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed) policycoreutils-python-2.5-11.el7_3.x86_64 libpython2.7.so.1.0()(64bit) is needed by (installed)
[CentOS] Firefox 68 jnlp files
It seems that firefox 68.x, as distributed with CentOS6 updates, no longer allows opening jnlp files with javaws The "Choose Helper Application" window popping up after selecting "Open with/Other" has a predefined list of applications that cannot be customised. I'm sure it must be a configuration issue as this works fine with the same browser on other distributions, but what to look for? # alternatives --display javaws javaws - status is auto. link currently points to /usr/java/latest/jre/bin/javaws /usr/java/latest/jre/bin/javaws - priority 20 Current `best' version is /usr/java/latest/jre/bin/javaws. # ll -L /etc/alternatives/javaws -rwxr-xr-x 1 root root 140296 Dec 15 2018 /etc/alternatives/javaws # ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 for armv7hl
> Hello together > > were can I find any information on working on Centos 8 for ARM 7 ? I can't > find anything. Hi Andreas, There is a CentOS Arm Dev list where you can discuss that topic. You can subscribe at: https://lists.centos.org/mailman/listinfo/arm-dev Best, Patrick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] printer only prints one page, if anything
> I had tried that also, but tried it again. > before my last try, I power-cycled the printer. > This time it worked. > For some reason CUPS now shows two queue names: > HL-L2360D-series Brother HL-L2360D series localhost.localdomain > HL-L2360D HLL2360D > both Brother HL-L2360D for CUPS. > > 'Tain't as big a deal as having none, > but why does CUPS have two queue names for the printer? Do you have CUPS autodiscover turned on? (AKA Avahi on Linux systems), if so CUPS will have automatically added the printer in addition to the one you manually added. > > I think they were the same packages that I tried to use. > In any case, they both ended in 386. Once again, do you have a 64 bit system? If so, then any executables in the RPMs won't work unless you have added the 32-bit compatibility stuff. RPMs aren't magic, they need to have the requirements added by the packager and if the requirements aren't mentioned in the RPM, it will still install, but none of the executables will run. They will come up with Bad ELF errors. > > Had not heard of system-config-printer . > Neither man, info nor --help helped. > What is it suppoded to do? > Google suggests it is a GUI. > Google also suggests that it is always started through a GUI. The god Google is not infallible. system-config-printer is the old way of adding and managing printers. It's a GUI, but you can start it from a command line in a GUI environment (i.e. it's not a command line program). But it's just a front end, you still need the underlying drivers there before it can configure a printer. However, system-config-printer is deprecated in CentOS 7 and I believe it's not in CentOS 8 (I could be wrong though). The official way to manage printers in CentOS 8 is either via CUPS or cockpit. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 8 for armv7hl
Hello together were can I find any information on working on Centos 8 for ARM 7 ? I can't find anything. Mit freundlichen Grüßen / Kind regards Andreas Reschke ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] printer only prints one page, if anything
On Wed, 2019-11-06 at 17:16 -0600, Michael Hennebry wrote: > On Wed, 6 Nov 2019, Fred Smith wrote: > > > It looks as if you downloaded the two RPMs from Brother then > > attempted > > to follow their complicated instructions for installing them. Much > > simpler is to do this: > > > > linux-brprinter-installer-2.1.1-1 is the brother printer driver > > installer I used on my HL-L2360D. > > I had tried that also, but tried it again. > before my last try, I power-cycled the printer. > This time it worked. > For some reason CUPS now shows two queue names: > HL-L2360D-series Brother HL-L2360D series localhost.localdomain > HL-L2360D HLL2360D > both Brother HL-L2360D for CUPS. > > 'Tain't as big a deal as having none, > but why does CUPS have two queue names for the printer? I dont't have any Brother printer to test ths but was the printer USB connected when you ran the setup? If so, one may be the network connection (the first entry) and the second one the same printer over USB? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
