Multi-monitor configuration oddness
by Jeffrey Ross
I have a laptop (Lenovo T440P) with the Ultra dock docking station. I
have 2 monitors connected to the docking station both via a the display
port interfaces, and the monitors work fine, the system recognizes them
as screen numbers 2 and 3.
The problem is when the system boots up the system identifies the screen
on the closed lid as a valid and active monitor and puts the login
screen on that monitor while displays 2 and 3 are on but blank. Once I
log in (blindly) the system will properly recognized that the lid
monitor is not active only display on #2 & 3, and in fact if I choose
"Displays" it will show that monitor #1 is a "Built-in display" and list
it as off.
I am using the default Gnome desktop with the current updates for Fedora 25.
I'm going to guess there is a simple tweak someplace that I'm missing.
Thanks, Jeff
6 years, 11 months
crond stopped, still fills /var/log/messages with millions of
messages
by M. Fioretti
Greetings,
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but the only line in my own crontab is a shell script that runs every
minute. When I run that script manually, from the command line, it yelds
no error or warning. From what I can see, this flood of crond warnings
started about a week ago, but I've used
that computer almost nothing in the last two weeks.
I should install a local MDA on this box, I guess, but before that I
should really figure out what is making crond try 20 times a second to
send an email, and make it
stop. Any ideas?
TIA,
Marco
--
http://mfioretti.com
6 years, 11 months
State of scim in Fedora
by Sam Varshavchik
I'm wondering if anyone is still using scim successfully in Fedora, and
still finds it functional.
I'm hacking my own IM code. I have it working, more or less, with ibus; but
I thought it would be good idea to also try it with other IM server. I saw
that scim is still packaged for Fedora; I uninstalled all the ibus packages
and then installed all the scim packages.
After rebooting, the first thing that was apparent is that the input method
server was not getting started when I logged into the desktop (XFCE), and I
couldn't find any panel icon to switch input methods.
Ok, so I ran scim-setup. Then I started scim manually from a terminal, but
despite configuring, in scim-setup, the hotkey to switch input methods, I
could not get any response to the hotkey using existing clients that I know
are IM-enabled. Trying to run my own code, I could see that it has no issues
connecting to scim, and negotiating the protocol, but then scim stops
responding to all further messages.
After tinkering around, and not making much progress, I uninstalled scim,
and reinstalled ibus. After a reboot, ibus started right up, with my old
ibus configuration, and my IM code was fine, once more.
So, I'm not sure whether this is the case of scim not working with XFCE;
whether I'm missing a package that needs to be installed; whether all the
scim packages are there just because they still build; or something else.
6 years, 11 months
failure when logging into redhat.bugzilla.com
by patman@aracnet.com
I tried emailing bugzilla-requests(a)redhat.com about this, but the email bounced :-(
Is anyone else having issues logging into redhat.bugzilla.com?
Should I open a bug for this? ;-)
I'm getting the following when I try to login (to https://bugzilla.redhat.com ):
An unexpected error occurred. This could be a temporary problem, or some code is behaving incorrectly. If this problem persists, please email this page to bugzilla-requests(a)redhat.com with details of what you were doing at the time this message appeared.
URL: https://bugzilla.redhat.com/index.cgi
An error occurred while performing a database operation:
DBD::Pg::db do failed: ERROR: cannot execute DELETE in a read-only transaction [for Statement "DELETE FROM login_failure WHERE user_id = ? AND ip_addr = ?"] at /var/www/html/bugzilla/Bugzilla/User.pm line 2273
Bugzilla::User::clear_login_failures('Bugzilla::User=HASH(0x7f727e242e30)') called at /var/www/html/bugzilla/Bugzilla/Auth/Verify/RedHat.pm line 146
Bugzilla::Auth::Verify::RedHat::check_credentials_password('Bugzilla::Auth::Verify::RedHat=HASH(0x7f727d848cd0)', 'HASH(0x7f727e23e8d0)') called at /var/www/html/bugzilla/Bugzilla/Auth/Verify/RedHat.pm line 56
Bugzilla::Auth::Verify::RedHat::check_credentials('Bugzilla::Auth::Verify::RedHat=HASH(0x7f727d848cd0)', 'HASH(0x7f727e23e8d0)') called at /var/www/html/bugzilla/Bugzilla/Auth/Verify/Stack.pm line 53
Bugzilla::Auth::Verify::Stack::check_credentials('Bugzilla::Auth::Verify::Stack=HASH(0x7f727e3864c0)', 'HASH(0x7f727e23e8d0)') called at /var/www/html/bugzilla/Bugzilla/Auth.pm line 57
Bugzilla::Auth::login('Bugzilla::Auth=HASH(0x7f727dbffd70)', 2) called at /var/www/html/bugzilla/Bugzilla.pm line 492
Bugzilla::login('Bugzilla', 0) called at /var/www/html/bugzilla/index.cgi line 31
ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::var_www_html_bugzilla_index_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7f727e5b3428)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('Bugzilla::ModPerl::ResponseHandler=HASH(0x7f727de40908)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('Bugzilla::ModPerl::ResponseHandler=HASH(0x7f727de40908)') called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('Bugzilla::ModPerl::ResponseHandler', 'Apache2::RequestRec=SCALAR(0x7f727e5b3428)') called at /var/www/html/bugzilla/mod_perl.pl line 134
Bugzilla::ModPerl::ResponseHandler::handler('Bugzilla::ModPerl::ResponseHandler', 'Apache2::RequestRec=SCALAR(0x7f727e5b3428)') called at -e line 0
eval {...} called at -e line 0
Traceback:
at /var/www/html/bugzilla/Bugzilla/DB.pm line 202
Bugzilla::DB::_handle_error(...) called at /var/www/html/bugzilla/Bugzilla/User.pm line 2273
Bugzilla::User::clear_login_failures(...) called at /var/www/html/bugzilla/Bugzilla/Auth/Verify/RedHat.pm line 146
Bugzilla::Auth::Verify::RedHat::check_credentials_password(...) called at /var/www/html/bugzilla/Bugzilla/Auth/Verify/RedHat.pm line 56
Bugzilla::Auth::Verify::RedHat::check_credentials(...) called at /var/www/html/bugzilla/Bugzilla/Auth/Verify/Stack.pm line 53
Bugzilla::Auth::Verify::Stack::check_credentials(...) called at /var/www/html/bugzilla/Bugzilla/Auth.pm line 57
Bugzilla::Auth::login(...) called at /var/www/html/bugzilla/Bugzilla.pm line 492
Bugzilla::login(...) called at /var/www/html/bugzilla/index.cgi line 31
ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::var_www_html_bugzilla_index_2ecgi::handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 31
ModPerl::Registry::handler(...) called at /var/www/html/bugzilla/mod_perl.pl line 134
Bugzilla::ModPerl::ResponseHandler::handler(...) called at -e line 0
eval {...} called at -e line 0
6 years, 11 months
Re: latest update break F25
by stan
On Fri, 21 Apr 2017 23:52:47 +0200
gil <puntogil(a)libero.it> wrote:
Il 22/04/2017 6.16, stan ha scritto:
> On Thu, 25 Aug 2016 12:43:59 +0200
> gil <puntogil(a)libero.it> wrote:
>
>>> hi
>>> yesterday i update my system (F25, 32 bit) but i can no more use it
>>> now i download latest F25 iso for 64 bit but after update task i
>>> have
>>> the same problem
>>> any ideas?
>> What happens? What is the 'same problem'? Does it crash? Does it
>> hang? I have a 64 bit F25 that is working just fine, so it must be
>> something particular about your system.
>>
>> What hardware do you have? What desktop are you using?
> dracut-initqueue[313] could not boot ... /dev/fedora/root does not
> exist ... /dev/fedora/swap does not exist ... /dev/mapper/fedora-root
> does not exist
> i using kde
> motherboard asrock 870 extreme3 + sb 850 chipset
> cpu athlon x4 640
> grafic card gt 710 geforce nvidia
There shouldn't be a problem with that hardware. What kind of boot
device?
I'm operating in unfamiliar territory here, so be cautious with my
advice. These links seems to have information related to your
problem. Which appears to be that dracut is pointing to a non-existent
partition to boot from. Did you do anything unusual to your storage
before this started happening?
And just to be sure, when you say update, do you mean package update
(get latest packages) or version update (change from earlier version
of Fedora to Fedora 25)?
http://forums.fedoraforum.org/showthread.php?t=292910
https://blogs.fsfe.org/samtuke/?p=665
Moving this to users, where someone else is more likely to be able to
help.
6 years, 11 months
Customize gnome initial setup
by oscar.segarra@gmail.com
Hi,
I'd like to create a custom distribution of fedora and I'd like to add more questions in the gnome initial setup. I mean, as I want to create an OEM distro, the gnome-initial-setup will have to be able to configure network, or set the default url for firefox , or add some lines to an /etc/myapp/myapp.conf file (between some others).
Any advice about how to achieve this will be welcome
Thanks a lot.
6 years, 11 months
OT: FF problem
by JD
Aiming the browser at astrobix.com was working find for the past
few years I have been using it.
Today, it started giving me this (it is assuming I am onwindoze):
Server Error in '/' Application.
Could not load file or assembly 'System.Web.WebPages.Razor,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or
one of its dependencies. The located assembly's manifest definition does
not match the assembly reference. (Exception from HRESULT: 0x80131040)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or
assembly 'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located
assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)
Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to
determine why the assembly 'System.Web.WebPages.Razor, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].
Stack Trace:
[FileLoadException: Could not load file or assembly
'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located
assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)]
Microsoft.Web.WebPages.OAuth.PreApplicationStartCode.Start() +0
[InvalidOperationException: The pre-application start initialization
method Start on type
Microsoft.Web.WebPages.OAuth.PreApplicationStartCode threw an exception
with the following error message: Could not load file or assembly
'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located
assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040).]
System.Web.Compilation.BuildManager.InvokePreStartInitMethodsCore(ICollection`1
methods, Func`1 setHostingEnvironmentCultures) +613
System.Web.Compilation.BuildManager.InvokePreStartInitMethods(ICollection`1
methods) +141
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String
preStartInitListPath, Boolean& isRefAssemblyLoaded) +102
System.Web.Compilation.BuildManager.ExecutePreAppStart() +157
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager
appManager, IApplicationHost appHost, IConfigMapPathFactory
configMapPathFactory, HostingEnvironmentParameters hostingParameters,
PolicyLevel policyLevel, Exception appDomainCreationException) +531
[HttpException (0x80004005): The pre-application start initialization
method Start on type
Microsoft.Web.WebPages.OAuth.PreApplicationStartCode threw an exception
with the following error message: Could not load file or assembly
'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located
assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040).]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +9946132
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +90
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest
wr, HttpContext context) +261
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET
Version:4.6.1087.0
6 years, 11 months
laptop HDD continually parking/waking (Fedora 25)
by Tim
I thought that something had been done to stop this continual parking
and waking of the hard drive on laptops, in recent Fedora releases. In
the past, I added a hdparm command to /etc/rc.local, but I was under the
impression that laptop installations were meant to be a bit smarter
about this, later on.
It's annoying to hear it going click/whirr every few seconds, and is
going to prematurely wear out the drive. Not to mention that there's
zero point in putting a drive into standby if you're only going to keep
poking at it every few seconds. And, quite frankly, I don't see why the
OS should be doing that, either.
This is on a fairly basic new install. I haven't intentionally
installed something that ought to be continually running in the
background.
--
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
The mindset of software designers: You know that feature that you, and
many thousands of other users, found useful? We removed it, because we
didn't like it. We also hard-coded the default settings that you keep
customising.
6 years, 11 months