Bug 10576 - Mageia's gvim -u NONE -U NONE (also as a new user + on LXDE) emits warnings
Summary: Mageia's gvim -u NONE -U NONE (also as a new user + on LXDE) emits warnings
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-20 23:02 CEST by Shlomi Fish
Modified: 2015-09-21 13:35 CEST (History)
0 users

See Also:
Source RPM: vim-7.3.1036-1.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Shlomi Fish 2013-06-20 23:02:26 CEST
Description of problem:

When I run Mageia's gvim from an X-window terminal (such as LXTerminal or Konsole) - including in a new user and in LXDE,  it emits warnings to the screen:

shlomif@telaviv1:~$ gvim -u NONE -U NONE

(gvim:16772): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(gvim:16772): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(gvim:16772): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(gvim:16772): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
shlomif@telaviv1:~$ 

This does not happen with a gvim that I compiled from source under a prefix. Rebuilding vim on my system does not fix the problem.

This started happening a few days ago (possibly after I installed task-gnome-minimal). Furthermore, Running "gedit" does not emit any warnings.

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

Cauldron.

How reproducible:

Always.

Steps to Reproduce:
1. sudo urpmi vim-X11.
2. Run gvim from a terminal.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-05-17 21:28:16 CEST
still valid in Mageia 4. Is it in Mageia 5 too?

Keywords: (none) => NEEDINFO
Whiteboard: (none) => MGA4TOO

Comment 2 Shlomi Fish 2015-05-18 12:39:40 CEST
(In reply to Samuel VERSCHELDE from comment #1)
> still valid in Mageia 4. Is it in Mageia 5 too?

It does not appear to be valid in Mageia 5 from what I tried. I've made this bug "Mageia 4"-only.

Keywords: NEEDINFO => (none)
Version: Cauldron => 4
Whiteboard: MGA4TOO => (none)

Comment 3 Samuel Verschelde 2015-09-21 13:21:33 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 4 Shlomi Fish 2015-09-21 13:35:03 CEST
Does not happen in Mageia 5 and later, so closing.

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


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