[Bug 272147] New: yakuake 2.8.0 beta from kde buildtree does not save its access key
https://bugzilla.novell.com/show_bug.cgi?id=272147 Summary: yakuake 2.8.0 beta from kde buildtree does not save its access key Product: openSUSE 10.2 Version: Final Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: admin@eregion.de QAContact: qa@suse.de yakuake from buildtree forgets its access key on restart, making it useless; i have to do "dcop yakuake DCOPInterface slotToggleState" to roll it down, to configure the access key again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 stbinner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |dkukawka@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 ------- Comment #1 from admin@eregion.de 2007-05-08 02:27 MST ------- now that 2.8.0 beta broke the accesskey config, not even going back to 2.7.5 from boxed 10.2 helps; that version also forgets the access key. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #2 from dkukawka@novell.com 2007-05-08 06:16 MST ------- I can't reproduce the behavior you discriped. Not on 10.2/SLED10/SLED10SP1/Factory. Not with already installed older version and then updated and also not if fresh installed the package from KDE-backports. Maybe you should remove ~/.kde/share/config/yakuakerc and reinstall the complete package. Yakuake should ask you on start for the access key (default is F12). Btw. updates from KDE-Backports are _complete_ unsupported. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Comment #3 from admin@eregion.de 2007-05-08 07:28 MST ------- 1. i went back to yakuake 2.7.5 from boxed 10.2 AS I SAID BEFORE. Same behaviour. 2. removed yakuakerc, didnt help. on startup (even with yakuake 2.7.5 from boxed 10.2, you know, the version that you pay money for) it comes up with a little popup saying "application started, press to use it" and the two blanks should be around the key. and i _know_ about the "unsupported" status, but i did not think that means that you guys dont even want to know if the stuff works at all, or not. name any other reliable way to tell you guys about broken packages in backports and i'll use that way instead. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Minor ------- Comment #4 from dkukawka@novell.com 2007-05-08 08:28 MST ------- 1.) went back from a newer to an old version is not really supported, because you never can say if this work. You simply destroyed your installation of yakuake. This is no valid scenario. 2.) Do this: - stop/kill yakuake - rpm -e yakuake - remove ~/.kde/share/config/yakuakerc - remove /opt/kde3/share/config.kcfg/yakuake.kcfg - install 2.8Beta1 with rpm -ihv - check if this work now if you start yakuake --> if this not work: kill yakuake, add "AccessKey=F12" to Section [Global Shortcuts] in ~/.kde/share/config/yakuakerc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 ------- Comment #5 from admin@eregion.de 2007-05-08 09:01 MST ------- 1.) shouldn't that better be _not_ the case when you upgrade stuff through rpm packages? 2.) followed these instructions. after installing 2.8 beta, yakuake asked me for the access key on first start. I configured F12 and it worked. killed yakuake, started it again, it came up with no access key at all. killed it again and put the access key in the yakuakerc file, it worked. even after restarting yakuake. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Comment #6 from dkukawka@novell.com 2007-05-08 09:07 MST ------- 1) what you did was not a update it was a downgrade and update to complete new versions could cause such problems. 2) if you kill yakuake instead of end it correctly such things can happen. Maybe the config get written only on exit. Close the bug again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Comment #7 from admin@eregion.de 2007-05-09 02:30 MST ------- bad choice of words on my side, perhaps... i didnt "kill" yakuake with a -SIGTERM or something like that, i clicked its "quit" button. and the config GOT written, i had a yakuakerc after that that looked perfectly healthy to me, even when comparing to a working yakuakerc on a deifferent box, yust without that accesskey setting. hence, reopen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |admin@eregion.de ------- Comment #8 from dkukawka@novell.com 2007-05-15 12:29 MST ------- Please check if the yakuake package from my home project solve the problem: http://software.opensuse.org/download/home:/dkukawka/openSUSE_Factory/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|admin@eregion.de | ------- Comment #9 from admin@eregion.de 2007-05-16 03:34 MST ------- yep, with that version its working fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #10 from dkukawka@novell.com 2007-05-16 04:39 MST ------- submitted new package to Factory/STABLE -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272147 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com