Bug 12949 - Window of systemsettings becomes frozen when clicking Audio & Video-settings on the left side
Summary: Window of systemsettings becomes frozen when clicking Audio & Video-settings ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: High critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2014-03-06 03:43 CET by Kristoffer Grundström
Modified: 2015-10-27 06:58 CET (History)
3 users (show)

See Also:
Source RPM: task-kde4
CVE:
Status comment:


Attachments

Description Kristoffer Grundström 2014-03-06 03:43:40 CET
Description of problem: I use MATE 1.6.0 with the 3.12.13 kernel in Mageia 4 on x86_64 arch.

I was trying to find a way to change the keyboard settings when it comes to Audio and what keys to press to if you would like to change volume up and down and just as I recalled that this setting is changed elsewhere I just found a freeze when you click Audio and Video settings.

I opened Program ->System tools ->System tools ->Multimedia and then I clicked on Audio and Video settings on the left side. That made the system settings window freeze. I had to force quit the window.

Version-Release number of selected component (if applicable): 4.11.4

How reproducible: I have reproduced this more than 2 times.

Steps to Reproduce:
1. Install Mageia 4 with GNOME, KDE4, MATE and CINNAMON on x86_64 arch.
2. Use all medias except Testing ones. 
3. Check that you're fully updated.
4. Login to MATE.
5. Open Program ->System tools ->System tools ->Multimedia and click on Audio and Video settings.

Reproducible: 

Steps to Reproduce:
Kristoffer Grundström 2014-03-06 03:45:29 CET

Keywords: (none) => USABILITY
Priority: Normal => High
CC: (none) => kristoffer.grundstrom1983
Hardware: i586 => x86_64
Source RPM: systemsettings => task-kde4

Comment 1 Kristoffer Grundström 2014-03-06 03:47:30 CET
I didn't know what version I should've entered at Version-Release number of selected component (if applicable) so I wrote the version-number of KDE4 since systemsettings is a part of KDE4 even thou I opened it in MATE.
Comment 2 Atilla ÖNTAŞ 2014-03-14 10:04:22 CET
Do you see any errors in "journalctl" logs or "~/.xsession-errors" related to systemsettings freeze?

May i ask why do you tried to change media-keys from systemsettings instead of Mate Control Center > Keyboard shortcuts? I think there is nothing to do with systemsettings since it is a tool for completely different desktop environment. You should use MATE Control Center for this...

CC: (none) => tarakbumba

Comment 3 Kristoffer Grundström 2014-03-15 03:36:26 CET
I could not find anything related to system-settings, but what to look for then?
Comment 4 Olivier FAURAX 2015-01-05 14:59:20 CET
Can you try to launch systemsettings from command line to see if you get some error codes?

CC: (none) => olivier

Comment 5 Samuel Verschelde 2015-09-21 13:21:45 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 6 Marja Van Waes 2015-10-27 06:58:43 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD


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