Bug 8392 - Docky installation on Openbox doesn't start automatically after loggin in
Summary: Docky installation on Openbox doesn't start automatically after loggin in
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Malo Deniélou
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2012-12-15 03:08 CET by Palm Pre
Modified: 2013-11-23 16:13 CET (History)
1 user (show)

See Also:
Source RPM: docky-2.1.3-1.mga2.src.rpm
CVE:
Status comment:


Attachments
Starting docky from terminal messages (1.30 KB, application/octet-stream)
2012-12-15 03:09 CET, Palm Pre
Details
Starting docky from terminal messages (1.30 KB, text/plain)
2012-12-15 03:11 CET, Palm Pre
Details

Description Palm Pre 2012-12-15 03:08:48 CET
Description of problem: Maagei2 was  installed from dual CD.

I switched to open box and installed docky there. Docky was configured to start automatically after login. Unfortunatelly, it  doesn't. I have to do it manually every time.

Swithing from ~/.config/autostart vs ~/.local/share/autostart (https://bugs.launchpad.net/docky/+bug/653981) doesn't help.

Just in case I attach terminal messages from docky start




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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Palm Pre 2012-12-15 03:09:48 CET
Created attachment 3246 [details]
Starting docky from terminal messages
Comment 2 Palm Pre 2012-12-15 03:11:44 CET
Created attachment 3247 [details]
Starting docky from terminal messages

Attachment 3246 is obsolete: 0 => 1

Comment 3 Manuel Hiebel 2012-12-25 14:47:58 CET
no errors in ~/.xsession-error.log ? (don't remember the exact name)
Comment 4 Samuel Verschelde 2013-08-28 19:02:28 CEST
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => pierre-malo.denielou

Comment 5 Manuel Hiebel 2013-10-22 12:09:51 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and 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.

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.

-- 
The Mageia Bugsquad
Comment 6 Manuel Hiebel 2013-11-23 16:13:27 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


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