Re: Tomcat
by Rahul Sadotra
Hi Michael,
--- Michael Folin <michael.folin(a)donator.se> wrote:
> how do I install Tomcat i fedora?
> can't find it during the installation
>
If you mean during the installation of Fedora Core
itself, then I don't think Tomcat is provided with
Fedora Core (please feel free to correct me if I'm
wrong).
This means you will probably need to download Apache
Jakarta Tomcat (either binaries, or the source which
you'll need to build) and install it.
Hope this helps.
All the best,
Rahul
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
2 days, 13 hours
cupsd spamming the journal
by Patrick O'Callaghan
I'm getting this in the journal (repeats once per second):
Sep 01 11:02:05 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:02:04 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:02:03 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:02:02 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:02:01 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:02:00 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:01:59 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:01:58 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:01:57 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:01:56 Bree cupsd[1156]: Expiring subscriptions...
Sep 01 11:01:55 Bree cupsd[1156]: Expiring subscriptions...
Any thoughts?
poc
8 months
SATA optical drives
by David Fletcher
I'm currently running FC5, will probably upgrade to F7 in a couple of months.
Unfortunately my CD/DVD rewriter appears to have died, before it's
even seen a dual layer disk :'(
SATA hard drives run without problems for me, but now that SATA
optical drives are starting to appear in the shops, would it be OK to
buy one of these and get rid of another wide ribbon cable?
Is anybody already running them with Fedora?
Thanks for any advice/experiences.
Dave F
11 months
Re: cisco ise
by Patrick O'Callaghan
On Tue, 2020-04-28 at 16:45 +0000, david richyad wrote:
> cisco ise helps safeguard your business. It lets you control access throughout your network, see the user and device details, and stop/contain any threats. You can also use it to enforce security policies throughout your network. As a result, it helps prevent any technical issues and strengthens your cybersecurity measures. In short, you can manage your network security with more ease. Everything can be handled in one place, as opposed to needing multiple different applications open at once.
>
> https://www.fieldengineer.com/blogs/cisco-ise-deployment-guide
Does this have anything to do with Fedora? Advertising is not
acceptable on this list.
poc
12 months
How do I do a group reinstall of Xfce?
by ToddAndMargo
Hi All,
I have both MATE and Xfce installed. If I boot
into MATE, such that Xfce is not running, or not
start a GUI at all, how do I do a group reinstall
of Xfce?
Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 year, 1 month
Shift+PrintScreen gone with F36?
by Frederic Muller
Hi!
Something I use almost daily and.. nothing happens now. Is there a
replacement shortcut or a way to enable it back?
Thank you.
Fred
1 year, 2 months
Fedora 36: suspend failed with "PM: Some devices failed to suspend,
or early wake event detected"
by Dario Lesca
When I try suspend with "systemctl suspend" my notebook Fedora 36
sometime do not suspend with "PM: Some devices failed to suspend, or
early wake event detected" error.
Someone can help me to resolve this issue?
Many thanks
Dario
#----------------------------
set 14 00:41:26 dodo.home.solinos.it kernel: PM: suspend entry (s2idle)
set 14 00:41:26 dodo.home.solinos.it kernel: Filesystems sync: 0.006 seconds
set 14 00:41:28 dodo.home.solinos.it kernel: Freezing user space processes ... (elapsed 0.005 seconds) done.
set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer disabled.
set 14 00:41:28 dodo.home.solinos.it kernel: Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
set 14 00:41:28 dodo.home.solinos.it kernel: printk: Suspending console(s) (use no_console_suspend to debug)
set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16
set 14 00:41:28 dodo.home.solinos.it kernel: PM: Some devices failed to suspend, or early wake event detected
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: fb: VPR locked, but no scrubber binary!
set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3: reset high-speed USB device number 4 using xhci_hcd
set 14 00:41:28 dodo.home.solinos.it kernel: ata1: SATA link down (SStatus 4 SControl 300)
set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.1: reset low-speed USB device number 6 using xhci_hcd
set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.2: reset high-speed USB device number 8 using xhci_hcd
set 14 00:41:28 dodo.home.solinos.it kernel: PM: resume devices took 1.418 seconds
set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer enabled.
set 14 00:41:28 dodo.home.solinos.it kernel: Restarting tasks ... done.
set 14 00:41:28 dodo.home.solinos.it gvfsd[219783]: PTP: reading event an error 0x05 occurred
set 14 00:41:28 dodo.home.solinos.it kernel: thermal thermal_zone9: failed to read out thermal zone (-61)
set 14 00:41:29 dodo.home.solinos.it bluetoothd[1739]: Controller resume with wake event 0x0
set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend exit
set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend entry (s2idle)
set 14 00:41:29 dodo.home.solinos.it kernel: Filesystems sync: 0.002 seconds
set 14 00:41:31 dodo.home.solinos.it kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer disabled.
set 14 00:41:31 dodo.home.solinos.it kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
set 14 00:41:31 dodo.home.solinos.it kernel: printk: Suspending console(s) (use no_console_suspend to debug)
set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16
set 14 00:41:31 dodo.home.solinos.it kernel: PM: Some devices failed to suspend, or early wake event detected
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: fb: VPR locked, but no scrubber binary!
set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3: reset high-speed USB device number 4 using xhci_hcd
set 14 00:41:31 dodo.home.solinos.it kernel: ata1: SATA link down (SStatus 4 SControl 300)
set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.1: reset low-speed USB device number 6 using xhci_hcd
set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.2: reset high-speed USB device number 8 using xhci_hcd
set 14 00:41:31 dodo.home.solinos.it kernel: PM: resume devices took 1.418 seconds
set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer enabled.
set 14 00:41:31 dodo.home.solinos.it kernel: Restarting tasks ...
set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
set 14 00:41:31 dodo.home.solinos.it kernel: done.
set 14 00:41:31 dodo.home.solinos.it gvfsd[219783]: PTP: reading event an error 0x05 occurred
set 14 00:41:31 dodo.home.solinos.it kernel: thermal thermal_zone9: failed to read out thermal zone (-61)
set 14 00:41:31 dodo.home.solinos.it systemd-sleep[225719]: Failed to put system to sleep. System resumed again: Device or resource busy
set 14 00:41:31 dodo.home.solinos.it kernel: PM: suspend exit
set 14 00:41:31 dodo.home.solinos.it bluetoothd[1739]: Controller resume with wake event 0x0
set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
set 14 00:41:31 dodo.home.solinos.it systemd[1]: Failed to start systemd-suspend.service - System Suspend.
set 14 00:41:31 dodo.home.solinos.it audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
set 14 00:41:31 dodo.home.solinos.it systemd[1]: Dependency failed for suspend.target - Suspend.
set 14 00:41:31 dodo.home.solinos.it systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
set 14 00:41:31 dodo.home.solinos.it ModemManager[1836]: <info> [sleep-monitor] system is resuming
set 14 00:41:31 dodo.home.solinos.it systemd-logind[1762]: Operation 'sleep' finished.
--
Dario Lesca
(inviato dal mio Linux Fedora 36 Workstation)
1 year, 6 months
mailman on Fedora
by Sjoerd Mullender
What's the deal with maintaining mailing lists on Fedora these days?
For years I've used mailman (first mailman2, now mailman3) on Fedora to
administer mailing lists. In mailman3, you also need postorius to
provide a web interface to users and hyperkitty to provide mail archive
support.
On Fedora 35, mailman2 isn't available anymore, so that's when I
switched to mailman3. The original Fedora 35 did not have postorius,
but that became available later. Hyperkitty on the other hand is not
available on fedora 35. I use an rpm that I built myself.
On Fedora 36, mailman3 can be installed, but both postorius and
hyperkitty (there it is in the repository) cannot. They both depend on
a too old version of django.
On Fedora 37 (I know, not released yet, so any complaints should go to
the testing list) none of the packages can be installed since they all
depend on python 3.10 and F37 will come with 3.11. The packages are
actually the unmodified F36 packages.
Do people use mailman3 on Fedora? If so, how?
Should I invest time in getting it to work in a python virtual
environment? And how would that work with SELinux?
This very mailing list (users(a)lists.fedoraproject.org) is managed with
mailman3, but does the system on which it runs run Fedora?
--
Sjoerd Mullender
1 year, 7 months