I'm running Fedora 35 on a Dell Precision 3541, dual booted with Windows 10. Total storage for the system is 1TB, the storage dedicated to Fedora is about 650 GB. The system has 16GB of RAM. The desktop is Gnome.
Whenever I try to launch Google Chrome, Chrome begins to load for a few seconds, then I get logged out of Fedora.
I tried reinstalling both Fedora 35 and Windows 10; the problem remains. Both OSes were reinstalled from the same media as the original installs.
When I ran:
journalctl | grep error,
lines such as:
Dec 27 19:51:44 fedora kernel: BTRFS error (device sda10): bdev /dev/sda10 errs: wr 0, rd 0, flush 0, corrupt 806, gen 0
dominated the output.
The output of:
mount | grep sda10
is
/dev/sda10 on / type btrfs (rw,relatime,seclabel,compress=zstd:1,space_cache,subvolid=258,subvol=/root)
/dev/sda10 on /home type btrfs (rw,relatime,seclabel,compress=zstd:1,space_cache,subvolid=256,subvol=/home)
Running:
ls -a /dev/sda10
outputs nothing.
I've tried uninstalling and reinstalling Chrome, with no effect.
Also, after I'd been having these problems for several days, the system firmware was updated. The updates had no visible effect on my issues.
ABRT reports that the failing component is gnome-shell.
I installed KDE Plasma and switched to it using switchdesk. The effect of this was to add new issues on top of the original one, which remained unaffected.
I reinstalled gnome-shell, and switched back to gnome.
I have two questions:
Does the "corrupt 806" in the output of journalctl above refer to a hardware or software error?
Can anyone point me to resources that will help me solve my issue(s)?
Many thanks in advance for your help or advice.
If you want to use old /home/username, best thing to do before adding it to newer installed GNU/Linux is to remove folder ~/.config, ~/.local, ~/.cache, any ~/.bashrc*, and any other dot files.
I think I've figured out the root of the issue, and a solution that fixes at least some of the problems I've been having.
My last Fedora installation was Fe33, and my user name was userA.
Before upgrading to Fe35, I backed up /home to an external drive.
Then I installed Fe35, and as it happens, used a different user name, userB.
Then I restored the contents of /home. :-(
This left me with thousands of text files, as well as environment variables, containing the path /home/userA. What a mess!
What I've done as a workaround is, in /home, run sudo ln -s userB userA.
That has solved a lot of problems; others might perhaps be fixed by updating environment variables, and removing and reinstalling programs, such as Chrome, which have not been working for me.
Not sure, but maybe you should update your BIOS first from Windows.
Download here: Dell Precision 3541.
Related
I am trying to install MySQL on a Windows 10 PC. I downloaded the installer package and followed those steps
Went to https://dev.mysql.com/downloads/windows/
clicked on "MySQL Installer"
Scrolled to Generally Available(GA) Releases section
Clicked on "Windows (x86, 32-bit), MSI Installer" (mysql-installer-community-5.7.21.0.msi) and it started the download.
Once the download was complete, I double clicked on the installer and it gave a usual pop-up for any installation like,"Do you want this app to make changes to your device?" after clicking on "yes" for the answer to this question, it shows "Please wait while Windows configures MySQL-Installer-community" like below screenshot.
And then it keeps showing this installation progress bar for a very long time. Like more than 7-8 hours and the installation never completes
So it seems something is wrong as I don't think MySQL installation needs this long time. I tried to restart my computer and then delete any files related to MySQL from my computer and then started the whole process of installation again. But no luck yet
Anyone has any suggestion on this or did anyone face this kind of issue before? If so, is there a fix or a work around for this?
ok. So finally this is how I resolved my issue. And I found the solution at https://bugs.mysql.com/bug.php?id=82004 . The solution to this problem is to close an open "Windows installer" (the one using 0 memory and CPU) via task manager and the installation should begin running as expected.
Alternative solution: Use an administrator command prompt to run the MySQL installer on Windows 10. Details:
(Note: if you have any problems in the following steps, you can try to restart your computer. Then restart the steps.)
Right-click the Start/Windows icon in the bottom-left corner of Windows.
Click: Windows PowerShell (Admin).
A window asks: Do you want to allow this app to make changes to your device? Click: Yes.
Change to the directory with the MySQL installer. For example, if you downloaded the MySQL installer, type something like:
cd C:\Users\my_username\Downloads\
(Note: To save some typing, you can type a few characters, and then press the tab key, to make Windows show you various auto-completion options.)
Run the MySQL installer. Type something like the following command---make sure to include the period and backslash at the beginning---and press Enter.
.\mysql-installer-community-8.0.11.0.msi
Note: The idea of using an administrator command prompt came from John Geffe, in the link below, which was cited in the answer written by the original poster (user8425592):
https://bugs.mysql.com/bug.php?id=82004
Bug #82004 MySQL Installer freezes during "Please wait while Windows configures..." phase
[6 Feb 3:58] John Geffe
To get past this problem I had to run the .msi installer from an the
Administrator command prompt. Hopefully this helps someone in the
future.
[19 Apr 18:14] Jim McCauley
John Geffe: Thanks! Your note on installing as an administrator seems
to have taken care of the problem.
this did the trick for me: https://ao.ms/mysql-community-server-msi-installer-hangs-on-windows-10/
run cmd (commandline) as Administrator
cd to your location that you downloaded the .MSI to
run the “msiexec” commandline tool with option “/i” as follows:
msiexec /i [replace with file name]
example: msiexec /i mysql-installer-community-5.7.20.0.msi
Another thing that worked for me was running the installer in compatibility mode for previous version of Windows. You can try that as well.
Go to the link you provided (the first one) and try installing MySql Workbench. That is the version that is commonly used, and one that I verified works in Windows 10. Here is the link: https://dev.mysql.com/downloads/workbench/
Obviously, make sure you choose the right architecture, have the correct permissions to install software, and have enough space on your hard drive, or on the machine you are installing to.
Please install "Update for Visual C++ 2013 and Visual C++ Redistributable Package" from Microsoft Site "http://download.microsoft.com/download/0/5/6/056DCDA9-D667-4E27-8001-8A0C6971D6B1/vcredist_x64.exe"
Please look here at https://support.microsoft.com/en-in/help/3179560/update-for-visual-c-2013-and-visual-c-redistributable-package
Yes, I also got the same problem on my Windows 10.
Followed the Powershell solution and it worked.
Just repeat the above:
Click Start on bottom left corner
Scroll down the application list until Windows Powershell
Select Windows Powershell again on sub-menu
Type in cd (to change to your .msi folder)
Type .\xxxxx.msi (this is the installer file name)
All good.
Once you install the above package run the installer again and do the steps. You will be able to install the mysql-installer-community-5.7.21.0 for 64 bit windows 10
closing Windows Installer instances using 0 memory and CPU helps me to get past this problem.
For me on Window-10 machine, there was a problem with the "mysql-connector-net-8.0.11.msi". I was not able to uninstall this and hence all my subsequent efforts to install MySQL were failing. I did the following to overcome this issue.
Re-installed "mysql-connector-net-8.0.11.msi" Get it here and used the 'Repair' option
Installed the "mysql-installer-web-community-8.0.11.0.msi"
These two things solved my problem. Hope this helps.
The reson is your antivirus didn't allow the mysql, so Disable protection(until restart),( in your task bar right side click the arrow and right click to antivirus,to select (Disable protection(until restart)).then restart your computer again install mysql installer it will work.
For this issue just run .msi file in command administration like
E:\mysql-installer-community-8.0.20.0.msi\
follow this link:
https://kb.foxitsoftware.com/hc/en-us/articles/360040660611-How-to-install-MSI-from-command-line-with-administrator
In my case, an upgrade to 5.7.29 on Windows 10 via mysql-installer-web-community-8.0.20.0.msi, the install froze "backing up the database". The log tab showed no activity for 8 minutes. I clicked on cancel, then at the "are you sure" prompt I declined to cancel, and all of a sudden the install was working again. Very strange...
I encountered the same problem, preparing but can never get started. Tried to close other installation programs with no use, but I took the inspiration and proceeded with restart the computer and it worked nicely. So, I think the issue is to get rid of everything that could be in the background running that somehow interferes the installation.
You should run the installer as an administrator but this specific installation may not provide an option for this. Some might have it but it's most likely that it's unavailable for many users. So you should run it in cmd or powershell. And don't forget to run these shells as an administrator coz that's the whole point here. Once there, navigate to the installer's location which usually is in the downloads directory and run it using this command ./name.msi
Make sure no other ongoing installation of this instance. Close it if there exists one and undo the changes made by uninstalling it from the panel. If still facing difficulties, try restarting your machine and repeat this procedure...
Have fun
I had the same Problem, A simple solution is to give access the "SYSTEM" to the msiserver...I know, this is hard to understand what I am saying....You can Simply see this Video and you will definitely find the answer https://www.youtube.com/watch?v=6SdXMjXmnUk, It is a matter of just 3 minutes...
I encountered the same issue of taking too much time to install mysql community installer.I tried 3 times by cancelling the installation and restarting to perform a new installation.But had same issue. I tried 2 things
First to end all tasks associated with installation which I performed for installing mysql using Task Manager
Reinitiated the installation but didn't solved my issue.
Secondly tried to install through Windows Powershell as admin, which solved the problem.
Click on the Windows icon/start on the bottom left corner.
Right click and select the option Windows Powershell (Admin).
A pop up window will ask Do you want to allow this app to make changes to your device?....Click Yes.
Now cd to your downloads folder/wherever you downloaded the .msi file (For example cd C:\Users\MYPC\Downloads).
Once you reach to the folder where the .msi file is kept, run the following command.
.\mysql-installer-web-community-8.0.23.0.msi (Note: this is the version which I have downloaded, modify as your version).
while using the vmware tools distributed with the vmware player 12, it always came the error 'unable to start vmware-tools.service execution aborted', no matter what way I tried(even reinstalled the guest os). Finally I gave up and tried to use the open-vm-tools distributed with the fedora os. It is so simply working just by typing a command! Like this:
vmhgfs-fuse /mnt/hgfs
and then I found my shared folder name in hgfs!
Amazing!
If you're still puzzled by the official vmware-tools, and driven crazy by all kinds of weird issues it has caused, maybe you could try this way.
Just one step to share your files between host os and guest os.
PS:The way to set the shared folder is omitted.
As it turns out, Fedora 24 already ships with an open-source version of vmware tools, called open-vm-tools (and open-vm-tools-desktop). One way you can access shared folders is by opening a terminal and typing the following (as root)
sudo vmhgfs-fuse /mnt/hgfs
Then, your shared folders should be accessible in the hgfs folder.
I just installed a fresh copy of Fedora 24 Workstation and did a full dnf update on the entire system.
Then I installed the jProfiler rpm from the jProfiler site.
However, when I try to launch jProfiler (either from the /opt/jprofiler9/jProfiler.desktop icon or from /opt/jprofiler9/bin/jprofiler shell script), I get the following error message:
java.awt.HeadlessException
at java.awt.SplashScreen.getSplashScreen(SplashScreen.java:117)
at com.exe4j.runtime.splash.AwtSplashScreen.<init>(AwtSplashScreen.java:17)
at com.exe4j.runtime.splash.SplashEngine.setJavaSplashScreenConfig(SplashEngine.java:17)
at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:50)
I've tried setting my display using DISPLAY=0.0 or even DISPLAY=:0, but neither seem to make any difference/impact.
Any suggestions how to get this to work? I suspect it is something obvious that I am overlooking.
After a bunch of trial and error, I finally tried to install the Oracle Hotspot JRE instead of the OpenJDK JRE. I downloaded Oracle's JDK, installed it, and then configured it as the system default using:
sudo alternatives --config java
Now everything works properly with Oracle JRE.
I have a Lenovo Y510P with integrated IntelHD 4th gen. VGA and a dedicated Nvidia GT755 VGA.
I run Fedora 21 and until recently had no problems. I never installed any proprietary drivers or special tools to deal with graphics, it just worked under fedora.
(I use a Windows partition to play games, everything there works fine too.)
Quite recently I acquired a second GT755 for my Ultrabay-Slot. Booting to Windows went without a problem, SLI activated like a charm and everything seemed fine. However, booting to fedora caused the CPU to rapidly heat up. I found out later that having both VGAs installed causes the bios to disable IntelHD, which apparently was the only VGA Fedora can run out of the box.
So my first try was to install VGA drivers and IntelHD-drivers in parallel.
(following this guide: https://ask.fedoraproject.org/en/question/36506/changing-default-driver-for-displaying-x/ )
After I found out about the "no IntelHD with SLI"-problem I tried out to get the SLI disabled and rely only on my Intel. There I made a huge mistake:
In the bios, I disabled the GT755 while booting with only one VGA. Forgetting about that, I later tried to install the Nvidia driver again, which could not find the implemented GT755. Believing this was due to some xorg.conf-code within /usr/share/X11/xorg.conf.d/20-intel.conf:
Section "Device"
Identifier "Intel"
Driver "intel"
EndSection
I simply plugged in the second GT755, which caused the bios to disable IntelHD.
Now I installed the Nvidia Driver (bumblebee-nvidia) and everything worked fine, xorg.conf was rewritten autmatically, I disabled nouveau in /etc/default/grub and recompild grub (with grub2-mkconfig -o grub.cfg), and rebooted.
Since then, I could not get to the login-screen. When I enter my LUKS-passwd, I see a yellow Message:
[ 0.093961] Ignoring BGRT: invalid status 0 (expected 1)
But if I remember correctly, this was always displayed, just in white.
I have tried reverting to my backups of xorg.conf, grub.cfg and /etc/default/grub and recompiling grub, nothing worked.
Everything was tested with both enabled and disabled internal GT755.
I tried to reinstall bumblebee-nvidia with enabled GT755, no difference.
IntelHD drivers are loaded at startup and appear to be correctly configured in all xorg related confs.
Calling startx causes the login-screen to flash for a moment, just to be instantly replased by an error-message:
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
waiting for X server to shut down "sni-qt/[NUMBER, 4 digits]" WARN [TIMESTAMP] void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE bluedevil-monolithic: Fatal IO error: client killed(EE) Server terminated successfully (0). Closing log file.
At this point I would be glad to get my display back. Ideally however, I want to be able to keep the second VGA in it's slot and still use IntelHD, since I will never require high VGA performance under fedora.
What I need now is a possibility to revert my system back to it's old state.
With any luck I can actually install all required drivers afterwards and would write a little VGA-guide for the Y510P.
Apparently, I broke the displaymanager (sddm) somewhere somehow.
A friend helped me analysing the problem, but we were unable to find the exact cause.
We fixed the problem by replacing sddm with kdm.
the steps are:
install kdm
sudo yum install kdm
disable sddm:
sudo systemct disable sddm
reboot
I downloaded and installed MySQL 5.1.47 for OS X 10.6 using the DMG archive:
mysql-5.1.47-osx10.6-x86_64.dmg
I also installed MySQL.prefPane and MySQLStartupItem.pkg. MySQL.prefPane is a Preference Pane. The problem is, whenever I attempt to start/stop MySQL from the Preference Pane, System Preferences just hangs. It runs at about 50% CPU forever, eventually I have for force quit System Preferences. The same thing happens if I toggle "Automatically Start MySQL Server on Startup". Basically the MySQL Preference Pane is not functional.
Note that I have no problem starting MySQL from the command line:
sudo /usr/local/mysql/bin/mysqld_safe
I have tried reinstalling MySQL and the Preference Pane. I'm using the standard installation location, nothing out of the ordinary. Every time the MySQL Preference Pane just hangs.
I'm doing this on a Macbook Pro (Intel) running OS X 10.6.3. There are no old versions of MySQL on this machine.
Follow-up: Well it's now January 2012 so I figure I'd check to see if this has been fixed. I tried the latest MySQL 5.5.20 on OS X 10.6.8 and it's still broken - same behavior, it just hangs (had to force quit). I tried Jamie Wong's and carloandaya's suggestions, both did not work.
Under OS X Lion the following worked for me:
edit /usr/local/mysql/support-files/mysql.server
change lines ~ 46 & 47
basedir=
datadir=
to
basedir=/usr/local/mysql
datadir=/usr/local/mysql/data
For anyone still encountering this problem, see: http://bugs.mysql.com/bug.php?id=53232
Specifically, here's Rembert Oldenboom's response:
Issue still exists with mysql 5.5.8 on
brand new on mbp i7 2.8. With the
comments of others the fix was easy:
Edit
/usr/local/mysql/support-files/mysql.server
Search for "Set some defaults" about 4
lines down, replace the line
basedir=.
with
basedir=/usr/local/mysql
Then search for "Set pid file if not
given" about 3 lines down, replace the
line
mysqld_pid_file_path=$datadir/`hostname`.pid
with
mysqld_pid_file_path=$datadir/`/bin/hostname`.pid
Now the prefPane will work.
old stack overflow post! The world has changed a great deal, and I wanted to share my solution to this problem. The issue for me was the time zone tables AND Stephen's answers.
I did:
edit /usr/local/mysql/support-files/mysql.server
change lines ~ 46 & 47
basedir=
datadir=
to
basedir=/usr/local/mysql
datadir=/usr/local/mysql/data
AND updated my my.cnf.
I had a default-time-zone set to UTC. I had to comment out that line.
default-time-zone = UTC
to
# default-time-zone = UTC
Start server using plist file (check your plist path/name!):
sudo launchctl load -w /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
I then loaded MySQL time zone tables from Mac OS time zone files:
mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root --password="YOUR_PASSWORD_HERE" mysql
I then stopped MySQL and restarted using my plist file.
sudo launchctl unload -w /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
sudo launchctl load -w /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
After that, I was able to stop/start using the preference panel!
I've installed and re-installed MySQL 5.5.15 using some of the tips that I found on the net. I found that selecting "install for all users of this machine" rather than "install only for current user" after double-clicking the preferences pane installation from the .dmg file makes it work. It's the only step that I changed in my many installations of MySQL on Snow Leopard.
Are you sure that panther supports 64 bits apps ?
Seems that when a I'm trying to open a 32 bits preference pane on snow leopard, the preference pane says "well this pane is 32bits, and you've got a 64bits macos, I'm restarting this pane"
Maybe it's hanging because it's the opposite ? getting 32bits preference pane and trying to open a 64bits pane ?
I had this problem too. It turned out that I installed the 32 bit MySQL server on my 64 bit Mac on accident. Woops! I would recommend verifying your processor type (32 or 64 bit) and reinstalling the according MySQL DMG.
It took me a couple of days to figure this out! MySQL was still running fine in the background, it's just the preference pane and connecting to it via terminal that would not work.
I hope this works for you!
This worked for me :
sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start
Problem I recognised was of permission to mysql.server
Other solutions here didn't work for me, but I cobbled together my own solution with the help of this bug ticket: https://bugs.mysql.com/bug.php?id=28854 (specifically the comment by BuB Javier)
The trick was twofold:
Create a /bin/pidof file using the code from http://www.cs.cmu.edu/~benhdj/Mac/unix.html
#!/bin/sh
ps axc|awk "{if (\$5==\"$1\") print \$1}"|tr '\n' ' '
Make sure it's executable.
Create a /etc/my.conf or ~/.my.conf file with the pid-file option specifying the path to the PID file (e.g. /usr/local/mysql/data/`hostname`.pid). (This is easy to do within MySQLWorkbench.)
I discovered this after trying to stop the server in MySQLWorkbench and it throwing "PID file not found!" error messages. Apparently specifying the pid-file location in the mysql.server file doesn't work.
I did change some permissions to _mysql:wheel here and there as frequently suggested, but I'm not sure that mattered in my case. After doing the two steps above, the preference pane was working again. If it doesn't work for you, try changing some file permissions.
MySQL 5.6.25 Community Server (64bit)
Mac OS X Mavericks (10.9.5)