Bug 1030726 - At the core components of the ability to make some longer preloaded KDE.
Summary: At the core components of the ability to make some longer preloaded KDE.
Keywords:
Status: CLOSED DUPLICATE of bug 983110
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 02:58 UTC by Murzik2142
Modified: 2013-11-30 13:36 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-30 13:36:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
file /var/log/yum.log (191.42 KB, text/plain)
2013-11-25 18:29 UTC, Murzik2142
no flags Details

Description Murzik2142 2013-11-15 02:58:12 UTC
Description of problem:
When you boot from the new kernel more than 3.11.6-201.fc19.x86_64 stop working ability to make some components of KDE, such as the Startup menu, KDE, shutdown, restart, and so on.

Version-Release number of selected component (if applicable):
kernel 3.11.7-200.fc19.x86_64

How reproducible:
When choosing a new kernel than 3.11.6-201 cease preloaded ability to make some components of KDE,there is no sound kmix, I noticed only KDE startup menu and KDE (start, stop, etc.)

Steps to Reproduce:

1) Opt for the kernel in grub.
2) I enter my username and password in kdm.
3) Following the problem the lack of load conky (which is registered in the startup KDE), the lack of sound (solved manual start kmix), neriagiruet to press the menu button to turn off and etc.

Actual results:
1) Do not watch the lack of a running KDE startup conky.
2) There is no sound and the icon kmix.
3) There is no response to the shutdown, reboot and etc.

Expected results:

1) Running conky at startup
2) Having a sound and subsequent loading.
3) Can a KDE menu enable, disable, and etc.

Additional info:
journalctl -b
http://paste.fedoraproject.org/54200/44813071

Comment 1 Josh Boyer 2013-11-15 11:20:47 UTC
There's nothing in the log you pasted to indicate this is a kernel problem.  Even if there was, you have the virtualbox modules loaded and we don't support those.  Was there anything else updated at the same time the kernel was?  Can you attach your yum.log as a plaintext attachment?

Comment 2 Murzik2142 2013-11-15 12:01:47 UTC
I do not remember to be honest.
yum.conf: http://paste.fedoraproject.org/54270/84516415/
This is a problem in the past but not consistently manifested.

Comment 3 Murzik2142 2013-11-15 16:18:57 UTC
(In reply to Murzik2142 from comment #2)
> I do not remember to be honest.
> yum.conf: http://paste.fedoraproject.org/54270/84516415/
> This is a problem in the past but not consistently manifested.

*yum.log

Comment 4 Josh Boyer 2013-11-18 16:30:23 UTC
(In reply to Murzik2142 from comment #2)
> I do not remember to be honest.
> yum.conf: http://paste.fedoraproject.org/54270/84516415/
> This is a problem in the past but not consistently manifested.

That expired.  Can you just attach it in bugzilla as a plaintext attachment directly please?

Comment 5 Murzik2142 2013-11-25 18:29:40 UTC
Created attachment 828801 [details]
file /var/log/yum.log

Comment 6 Murzik2142 2013-11-25 18:34:05 UTC
The culprit of this situation is: KDM.

After replacing KDM on SLIM (dm), all the problems have ceased to appear.

Comment 7 Murzik2142 2013-11-26 02:12:56 UTC
This morning, this bug manifested itself again.
Treated restart DM (systemctl restart slim).
This method works 100%.
Also noticed a difference when loading indications KDE.
When bug downloaded all gradually.
With the excellent work load first one, then the other 4.

Comment 8 Kevin Kofler 2013-11-30 13:36:46 UTC

*** This bug has been marked as a duplicate of bug 983110 ***


Note You need to log in before you can comment on or make changes to this bug.