Description of problem: When starting chromium-browser in Openbox, LXDE or MATE (as far as I know), it pops-up an error window complaining about "xdg-settings: unknown desktop environment". Closing this window, it runs normally, but it repeats again when opening chromium settings. Version-Release number of selected component (if applicable): 40.22.2214.111-1 How reproducible: Every time chromium-browser is launched or settings page is accessed. Reproducible: Steps to Reproduce:
Assignee: bugsquad => cjw
I believe this change is caused by the updated xdg-utils package. Chromium runs: xdg-settings check default-web-browser chromium-browser.desktop The base mga4 package xdg-utils-1.1.0-0.0.git20121008.3.mga4 only writes an error message to stderr but the updated xdg-utils-1.1.0-0.0.rc3.3.1.mga4 also creates this pop-up dialog window.
Assignee: cjw => shlomifSummary: chromium-browser shows xdg-settings error pop-up on start in Openbox => updated xdg-settings creates notification window on error while base version only writes a msg to stderrSource RPM: chromium-browser-stable-40.0.2214.111-1.mga4.src.rpm => xdg-utils-1.1.0-0.0.rc3.3.1.mga4.src.rpm
CC: (none) => cjw
(In reply to Christiaan Welvaart from comment #1) > I believe this change is caused by the updated xdg-utils package. Chromium > runs: > > xdg-settings check default-web-browser chromium-browser.desktop > > The base mga4 package xdg-utils-1.1.0-0.0.git20121008.3.mga4 only writes an > error message to stderr but the updated xdg-utils-1.1.0-0.0.rc3.3.1.mga4 > also creates this pop-up dialog window. Hi, I cannot reproduce this problem with xdg-utils-1.1.0-0.0.rc3.3.1.mga4 on LXDE (installed using urpmi task-lxde ) and LXDM on a Mageia 4 x86-64 Virtual Box VM. I only get an error to STDERR. Regards, -- Shlomi Fish
You need to have zenity or kdialog installed to get the dialog I guess: exit_failure_operation_impossible() { if [ $# -gt 0 ]; then if which zenity > /dev/null 2> /dev/null; then zenity --error --text="xdg-settings: $@" elif which kdialog > /dev/null 2> /dev/null; then kdialog --error "xdg-settings: $@" else echo "xdg-settings: $@" >&2 fi fi exit 3 }
(In reply to Christiaan Welvaart from comment #3) > You need to have zenity or kdialog installed to get the dialog I guess: > > exit_failure_operation_impossible() > { > if [ $# -gt 0 ]; then > if which zenity > /dev/null 2> /dev/null; then > zenity --error --text="xdg-settings: $@" > elif which kdialog > /dev/null 2> /dev/null; then > kdialog --error "xdg-settings: $@" > else > echo "xdg-settings: $@" >&2 > fi > fi > > exit 3 > } Thanks for the information. I am now able to reproduce it, but it seems to exist in the upstream version. I guess I can try to workaround it, but it should be reported upstream. Regards, -- Shlomi Fish
(In reply to Shlomi Fish from comment #4) > (In reply to Christiaan Welvaart from comment #3) > > You need to have zenity or kdialog installed to get the dialog I guess: > > > > exit_failure_operation_impossible() > > { > > if [ $# -gt 0 ]; then > > if which zenity > /dev/null 2> /dev/null; then > > zenity --error --text="xdg-settings: $@" > > elif which kdialog > /dev/null 2> /dev/null; then > > kdialog --error "xdg-settings: $@" > > else > > echo "xdg-settings: $@" >&2 > > fi > > fi > > > > exit 3 > > } > > Thanks for the information. I am now able to reproduce it, but it seems to > exist in the upstream version. I guess I can try to workaround it, but it > should be reported upstream. > Workaround applied in the latest subrel to xdg-utils on Mageia 4 core/updates_testing: xdg-utils-1.1.0-0.0.rc3.3.2.mga5.x86_64.rpm I also committed the workaround in the Cauldron version. Please test: http://pkgsubmit.mageia.org/ . Regards, -- Shlomi Fish
please submit your patch upstream if not done already
CC: (none) => mageia
(In reply to Nicolas Lécureuil from comment #6) > please submit your patch upstream if not done already I'm not sure it's the right fix. It's a workaround. There should be a better way to fix it.
CC: (none) => vincent.dema+mageia
Marking as ASSIGNED.
Status: NEW => ASSIGNED
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/
RESOLVEDing as FIXED because it's fixed in Mageia 5.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
(In reply to Shlomi Fish from comment #10) > RESOLVEDing as FIXED because it's fixed in Mageia 5. Please also update the Version field when doing so (I've done it this time). Either it's RESOLVED FIXED for Mageia 5, or RESOLVED OLD for Mageia 4.
Version: 4 => 5