Bug 13178 - OnMouseMove for tTrayIcon does not work
Summary: OnMouseMove for tTrayIcon does not work
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Alex Loginov
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3454
  Show dependency treegraph
 
Reported: 2014-04-09 15:28 CEST by Alex Loginov
Modified: 2015-09-28 10:55 CEST (History)
0 users

See Also:
Source RPM: lazarus-1.0.12-2.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Alex Loginov 2014-04-09 15:28:57 CEST
Description of problem: If run any project with tTrayIcon, then no effect with OnMouseMove. It's upstream bug: http://bugs.freepascal.org/view.php?id=23217


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


How reproducible: always


Steps to Reproduce:
1. run lazarus
2. open project with tTrayIcon, run program
3. move mouse above tray - no effect.


Reproducible: 

Steps to Reproduce:
Comment 1 Alex Loginov 2014-04-09 16:21:41 CEST
I have uploaded a patched package for Mageia 4.

Suggested advisory:
========================

Updated lazarus package fix:

- Added patch, which fix OnMouseMove for tTrayIcon for qt4 and gtk2 (sent to upstream)
========================

Updated packages in core/updates_testing:
========================
lazarus-1.0.12-2.1.mga4.rpm

Source RPM: 
lazarus-1.0.12-2.1.mga4.src.rpm

Lazarus's project for QA: https://drive.google.com/file/d/0B6CY1Q0WgkewY3VmRThNNFRaak0/edit?usp=sharing

When you move mouse above tray, than program must finish.
Before update: nothing happens
After update: program finished

Assignee: loginov_alex => qa-bugs

Alex Loginov 2014-04-09 17:41:23 CEST

Blocks: (none) => 3454

Alex Loginov 2014-04-11 23:22:38 CEST

Assignee: qa-bugs => loginov_alex

Comment 2 Alex Loginov 2015-09-21 13:18:08 CEST
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:WONTFIX

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

Comment 3 Samuel Verschelde 2015-09-21 13:21:46 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/

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

Comment 4 Samuel Verschelde 2015-09-28 10:31:55 CEST
Alex, you are the one who reported the bug in the first place, so you know if it's valid or not :)
Comment 5 Alex Loginov 2015-09-28 10:55:26 CEST
It was fixed by upstream for Gtk2 and by our patch for qt.
It was fixed for mga5 in new lazarus's versions, we have Gtk2 lazarus, and our patch for qt is applied for package.
It's old for mga4 because of EOL.

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


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