Bug 24960 - mgaonline in taskbar spawns false 'no media configured' popups
Summary: mgaonline in taskbar spawns false 'no media configured' popups
Status: RESOLVED DUPLICATE of bug 24636
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-15 22:00 CEST by Tony Blackwell
Modified: 2019-06-22 00:44 CEST (History)
2 users (show)

See Also:
Source RPM: mgaonline
CVE:
Status comment:


Attachments
urpmi.cfg with some enabled media, with which the bug occurs (19.96 KB, text/plain)
2019-06-16 13:36 CEST, Marja Van Waes
Details
output of ls -l /var/lib/urpmi (5.19 KB, text/plain)
2019-06-21 13:35 CEST, Tony Blackwell
Details

Description Tony Blackwell 2019-06-15 22:00:05 CEST
Description of problem:  Package media editor in taskbar is a questionmark on a red background, and repeated grey popup windows say Warning: no medium found, You must add...
This is untrue.  Media have beeen added and are normally usable.

Popup is very confusing for new user, and popups repeat at sometimes frequent intervals.

We've discussed this in qa.  I've tried the suggestion there to use other than gdm display manager (which led to just-filed but 24959: Xorg display manager doesn't allow login!)  Using kacage media editor from a different display manager doesn't prevent the popups continuing to appear when back using gdm.

The appearance of package media editor in the taskbar is flakey: it can disappear for a while, but is back with its white questionmark on red background as I type this.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2019-06-16 13:36:28 CEST
Created attachment 11099 [details]
urpmi.cfg with some enabled media, with which the bug occurs

I see this, too, but don't think gdm causes it. I use sddm.

Maybe mgaonline has a problem talking to urpmi?

CC: (none) => marja11

Marja Van Waes 2019-06-16 13:37:43 CEST

Assignee: bugsquad => mageiatools
Summary: Mageia Package Media Editor spawns false 'no media configured' popups => mgaonline in taskbar spawns false 'no media configured' popups
Source RPM: (none) => mgaonline

Comment 2 Martin Whitaker 2019-06-16 13:57:24 CEST
1. Please show the output of

  ls -l /var/lib/urpmi

and

  cat /etc/security/msec/security.conf

2. When/how did you add the media (e.g. at end of install, from MCC started from desktop menu or shortcut, from command line)

CC: (none) => mageia

Comment 3 Tony Blackwell 2019-06-21 13:35:08 CEST
Created attachment 11120 [details]
output of ls -l /var/lib/urpmi

see attached 'urpmifiles' for output of ls -l /var/lib/urpmi
Comment 4 Tony Blackwell 2019-06-21 13:37:11 CEST
$ cat /etc/security/msec/security.conf
BASE_LEVEL=standard

media were added after reboot following initial install, from MCC started from desktop toolbar (xfce)
Comment 5 Martin Whitaker 2019-06-21 20:38:40 CEST
And were you starting Xfce from  GDM when you added the media?

Keywords: (none) => NEEDINFO

Comment 6 Tony Blackwell 2019-06-21 23:16:41 CEST
Yes, although had done classic install and selected the full range of desktops to install, I'd not actually used any of these - only xfce
Comment 7 Martin Whitaker 2019-06-22 00:44:34 CEST
OK, this is definitely a duplicate of bug 24636. You should be able to fix your existing system by going into "Configure media sources..." in MCC, removing the media, and then re-adding them (without leaving "Configure media sources...").

@Marja, check the file permissions in /var/lib/urpmi. If the files aren't world-readable, you'll see the same symptoms, even if the cause is different. One known cause is setting the msec security level to high (which I think is bug 9386).

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Keywords: NEEDINFO => (none)


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