Bug 276166 - Pager forgets how many rows it is configured to display.
Summary: Pager forgets how many rows it is configured to display.
Status: RESOLVED DUPLICATE of bug 273695
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-pager (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-21 04:50 UTC by dan hetherington
Modified: 2011-12-02 17:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dan hetherington 2011-06-21 04:50:55 UTC
Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

I really apologise if I'm reporting this in the wrong place.  Is kpager the same thing as pager?  If not, why is it seemingly impossible to report a bug against pager?  Pager reports its version as 1.0 in the Add Widgets brief description screen.

Sometimes, when I log in, (k?)pager has forgotten how many rows it is configured to display.  I have set it to arrange my virtual desktops in 2 rows, but sometimes it reverts to displaying them in 1.

This has happened occasionally since at least Slackware 13.0, ie at least 2 years.  It seems to have become more frequent since I've upgraded to Slackware 13.37 (KDE4.5.5).

Reproducible: Sometimes

Steps to Reproduce:
Log out and back in again.

Actual Results:  
Sometimes, virtual desktops are displayed in a single row, instead of 2 rows as configured.  When opening the configuration dialog, "Pager Settings", General tab, the Number of Rows option has reverted to 1, too.

Expected Results:  
I'd expect virtual desktops to consistently appear in one row, as configured.

I would provide configuration files if I could figure out definitively where to look.
Comment 1 Janet 2011-06-26 00:43:17 UTC
Duplicate of Bug 273013?
Comment 2 Gregor Tätzner 2011-12-02 17:23:12 UTC

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