Annoyances with mate DT
by JD
For a while (like a few weeks), mate was saving the apps running on the
DT when I shutdown the system, and they would be auto started on reboot.
Slowly, some apps no longer get started.
This behavior first manifested 2 or 3 months ago when the mate-terminals
would no longer be started on reboot.
Then it was ktorrent.
Now, added to that is smplayer.
I had raised a bug with mate, but the bug report was rejected.
I am on the verge of dumping Mate altogether. Cinnamon is just
not mature enough, and I literally detest gnome3. It does nothing
that I want or like.
Hope that future fedora users who want to switch to mate might
see this and decide if they still want to run mate.
9 years, 2 months
No graphics
by Patrick Dupre
Hello,
I cannot run in graphic mode in fedora 21!!!!!
It is an intel Q965 card
What would I do?
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
9 years, 2 months
DRM MM Objects?
by Andy Blanchard
Just upgraded a box at home to new hardware with embedded Intel
graphics (i5 Haswell), did a clean install of Fedora 21, and while
poking around trying to fix a few issues while rebuilding my config
spotted something I've not noticed before. With KDE running "lsof"
lists over a thousand entries like this:
Xorg.bin 659 662 root DEL REG 0,4
16016 /drm mm object
Xorg.bin 659 662 root DEL REG 0,4
16011 /drm mm object
kwin 964 zocalo DEL REG 0,4
38725 /drm mm object
kwin 964 zocalo DEL REG 0,4
19275 /drm mm object
QProcessM 964 986 zocalo DEL REG 0,4
19277 /drm mm object
QProcessM 964 986 zocalo DEL REG 0,4
47240 /drm mm object
These are the only three processes that appear to own these files, and
the number of entries appears to fluctuate as windows are
opened/closed, and other GUI events happen.
A Google search comes up with a bunch of stuff about memory leaks from
a few years ago, plus some documention on Kernel memory management,
but I couldn't find anything that explains what these "/drm mm object"
entries are, whether this is normal behaviour, or if there is
potentially a problem.
Any ideas?
--
Andy
The only person to have all his work done by Friday was Robinson Crusoe
9 years, 2 months
upgrade to 21
by Patrick Dupre
Hello,
I am trying a fedora 20 to fedora 21 for a DVD
I launched fedup --device /mnt/sr0 --product=nonproduct
Then I boot on fedup.
The installation started fine.
Then I lived.
When I returned, the machine had reboot on the DVD.
Hence I restarted the machine but there are non option to boot on the new
installation.
While https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_Fed...
says
Once the upgrade process has completed, the system will reboot and an option to boot Fedora 21 will be on the grub menu
while:
fedup.log says
[ 27.188] (II) fedup:message() WARNING: no new kernel will be installed during upgrade
Then I try to boot on the kernel 20
The boot was OK, It booted in text mode.
I run startx but no graphics !
I attach the log file
Anyway I check on the installed packages.
There is no kernel 21 installed !
Here is the end of the fedup.log:
[ 27.188] (II) fedup:message() WARNING: no new kernel will be installed during upgrade
[ 27.189] (II) fedup:<module>() /bin/fedup exiting cleanly at Sat Jan 31 17:15:57 2015
[ 0.160] (II) fedup:<module>() /usr/bin/fedup 0.9.0 starting at Sat Jan 31 17:48:51 2015
[ 0.266] (II) fedup.sysprep:remove_cache() removing /var/cache/system-upgrade
[ 0.296] (II) fedup.sysprep:remove_cache() removing /var/lib/system-upgrade
[ 0.297] (WW) fedup.util:rm_f() failed to remove /var/lib/system-upgrade: [Errno 30] Read-only file system: '/var/lib/system-upgrade/media/.discinfo'
[ 0.297] (II) fedup.sysprep:remove_cache() removing /var/cache/system-upgrade
[ 0.297] (II) fedup.sysprep:remove_cache() removing /var/lib/system-upgrade
[ 0.297] (WW) fedup.util:rm_f() failed to remove /var/lib/system-upgrade: [Errno 30] Read-only file system: '/var/lib/system-upgrade/media/.discinfo'
[ 0.297] (II) fedup.sysprep:misc_cleanup() removing symlink /system-upgrade
[ 0.298] (II) fedup.sysprep:misc_cleanup() removing /system-upgrade-root
[ 0.298] (II) fedup.sysprep:misc_cleanup() removing /lib/systemd/system/system-upgrade.target.requires
[ 0.299] (II) fedup:<module>() /usr/bin/fedup exiting cleanly at Sat Jan 31 17:48:51 2015
upgrade.log seems OK
Should I boot again on the fedup (21) kernel?
Thank for your help.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
9 years, 2 months
Akonadi errors?
by Timothy Murphy
When I go to the Akonadi Server Configuration on my Fedora-21/KDE laptop,
and click on Test, I get the following errors:
MySQL server log contains errors
Current Akonadi control error log found
Previous Akonadi control error log found
Checking these errors, I find:
~/.local/share/akonadi/db_data/mysql.err
Error: Table "mysql"."innodb_table_stats" not found.
~/.local/share/akonadi/akonadi_control.error
"akonadi_nepomuk_feeder" could not be found!
"akonadi_folderarchive_agent" could not be found!
Does everyone get these errors?
Do they matter?
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
9 years, 2 months
Another systemd annoyance
by Heinz Diehl
Hi,
tried to safely bring down a crashed Fedora 21 machine today, but M-sysrq
didn't do anything. After bringing the machine up again, the logs showed
that M-sysrq functionality was disabled. After investigating further, it seemed
that only Sysrq-S (emergency save) was actually working. In /etc/sysctl.d/01-sysctl.conf,
"kernel.sysrq=1" was present. It took me nearly 30 min. to find out that systemd
has it's own sysctl definitions, gladly ignoring/overwriting /etc/sysctl.d. In
/usr/lib/sysctl.d/50-default.conf, "kernel.sysrq=16" was set, which is what crippled
full sysrq functionality.
In addition, I'm curious what happens when the next systemd update gets pulled in.
Most probably, my manual settings will be overwritten with what systemd thinks
is good for the user..
9 years, 2 months
Why does Anaconda overrides user decisions?
by Sudhir Khanger
Hello,
1. Anaconda changes X in sdaX. If you make a choice on order of /boot, swap,
and / partitions, Anaconda changes the order. As long as layout is valid why
does Anaconda has to change it.
2. 4 primary partitions are allowed on a disk. If I do that Anaconda changes
it to 3 primary and 1 logical partition. Why?
3. There is no option to create a partition and leave it for future use. How
do I create a partition and not have to use it immediately.
--
Regards,
Sudhir Khanger,
sudhirkhanger.com,
github.com/donniezazen,
5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.
9 years, 2 months
Strange Firefox behaviour
by Heinz Diehl
Hi,
Firefox has three different possibilities in Edit -> Preferences -> General
to chose from what should happen when Firefox starts:
1. Show my homepage
2. Show a blank page
3. Show my windows and tabs from last time
When using 3., for a short time the "default home page" (start.fedoraproject.org) loads,
disappears and my tabs from last time get loaded. The same happens when I previously closed
Firefox with nothing opened: the default home pages flashes up, followed by a blank screen.
This didn't happen before, and the behaviour is f*** annoying. Tried to user-set browser.startup.homepage
without any effect, the default homepage came automagically back.
Can anybody see the same phenomenon? Does anybody know when this has been introduced?
Thanks,
Heinz.
9 years, 2 months
Re: fedora 21 booting error with 3.17 & 3.18 kernels-SOLVED- still need info
by Paul Cartwright
On 01/30/2015 11:47 AM, Terry Polzin wrote:
> On Fri, 2015-01-30 at 10:53 -0500, Paul Cartwright wrote:
>> I finally let the boot sequence error out, took about 5 minutes. I got
>> this line:
>> Dracut-initqueue[283] Warning: Cancelling resume operation. device not
>> found.
>>
>> then the next line showed the UUID, ending in c063. That was the OLD
>> swap partition. I rebuilt the swap partition, did the swapon, and added
>> that UUID to /etc/fstab. Still errored out with same error. I removed
>> the 3.18.3-201 kernel & headers & module, reinstalled them, and now it
>> works. where is that old swap info kept, if not in /etc/fstab?? I
>> grepped for c063 in /boot and found entries in System.map-3.18.3-201...
>> but I am not sure it was the actual swap partition.
>>
>>
>>
>>> running fedora 21 x86_64
>>> I was redoing my drive partitions, reran grub2-install, and now I get
>>> stuck, and the boot won't complete when I select any 3.17 or 3.18
>>> kernel. I have the latest 3.18.3-201 installed. 3.16 kernel booted..
>>> I see what looks like dracut errors. Not sure what to do, google wasn't
>>> much help.
>>> /var/log/messages shows:
>>> Jan 29 03:00:05 pauls-server systemd: Started dracut pre-mount hook.
>>> Jan 29 03:00:05 pauls-server systemd: Started dracut mount hook.
>>> Jan 29 03:00:05 pauls-server systemd: Starting dracut pre-pivot and
>>> cleanup hook...
>>> Jan 29 03:00:05 pauls-server systemd: Started dracut pre-pivot and
>>> cleanup hook.
>>> Jan 29 03:00:05 pauls-server systemd: Stopping dracut pre-pivot and
>>> cleanup hook...
>>>
>>>
>>> not very descriptive.. suggestions on where to look or what is wrong?
>>> right now I am booted into fedora 20, using the same /home.. it's just
>>> that not everything works..
>>> uname -a
>>> Linux pauls-server 3.16.7-200.fc20.x86_64 #1 SMP Thu Oct 30 18:12:41 UTC
>>> 2014 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>>
>>
>> --
>> Paul Cartwright
>> Registered Linux User #367800 and new counter #561587
>>
> Isn't it buried someplace in the /boot/grub2/grub.cfg file? That's why
> reinstall of the kernel fixed it.
I looked in grub.cfg didn't find it..
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
9 years, 2 months