I guess this bug can be closed because Breezy is not supported anymore
and I think hardly anyone is upgrading from Breezy to Dapper anymore.
This bug doesn't exist in later releases, please report if it does by
any chance.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Inval
Doing a migration could be rather tricky.
What do you think, guys? Converting X resources to gconf keys?
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
only some lines (3-5) of the ~/.xscreensaver file would be needed, converting
that would be trivial, but the way *how* to implement it is a bit tricky, i
dont want a permantent wrapper script around the screensaver daemon...
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31
My screensaver settings were lost as well.
Breezy - Dapper upgraded through dist-upgrade 10 minutes ago...Note that
mid-install, I noticed that it paused because it said that configuration files
were changed... (didn't write down which ones, although I should have).
I chose the packager'
there is no relation between xscreensaver and gnome-screensaver settings
(thats exactly what this bug is about) conffile prompts on package
upgrades are unrelated here.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (Ubuntu)
Status: Unconfirmed => Confirmed
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
You could convince upstream to fall back on .xscreensaver if /apps
/gnome-screensaver is empty.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
thats a good idea but sadly not as easy to implement as it sounds, you'd
need to patch gconf very intursively to achieve that
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
We could also have gnome-screensaver do that. We don't need to patch gconf at
all.
William knows about xscreensaver and likely wants his application to replace it.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
still i think g-s-s rather should go on using gconf, so either a script
or an g-s-s code enhancement is needed to transfer the ~/.xscreensaver
settings into gconf, other apps rely on the fact that gconf is used for
settings in gnome-screensaver
--
Settings lost during an upgrade
https://launchpad
That is exactly the right thing to do!
Here's some pseudocode:
1. Check if /apps/gnome-screensaver has entries
2. If yes, carry on.
3. If no, look for .xscreensaver. If you find that, import as many entries as
you can into /apps/gnome-screensaver.
That's a total win for everybody.
--
Settings
yup i totally agree and thats what i meant above with "its trivial", but
would you do it with a permanent wrapper or with a hack to g-s-s ? i
think both is suboptimal ... but what sucks least ?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
deskt
The solution with the least suckage is to get it in the gnome-screensaver
binary. That way, all distributions win, instead of us keeping around a
non-standard patch.
Anyway, it's not a hack. It's a migration tool. :)
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desk
touching user settings in a postinst of a package is a big nono
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case, my primary screensaver is "None" (blank screen). How hard
would it be to check for at least this case?
also, re: "touching user settings in a postinst of a package is a big
nono." While my settings may not have been touched in actuality, they
were effectively touched because I upgrad
Doing a migration could be rather tricky.
What do you think, guys? Converting X resources to gconf keys?
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
only some lines (3-5) of the ~/.xscreensaver file would be needed, converting
that would be trivial, but the way *how* to implement it is a bit tricky, i
dont want a permantent wrapper script around the screensaver daemon...
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31
My screensaver settings were lost as well.
Breezy - Dapper upgraded through dist-upgrade 10 minutes ago...Note that
mid-install, I noticed that it paused because it said that configuration files
were changed... (didn't write down which ones, although I should have).
I chose the packager'
there is no relation between xscreensaver and gnome-screensaver settings
(thats exactly what this bug is about) conffile prompts on package
upgrades are unrelated here.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (Ubuntu)
Status: Unconfirmed => Confirmed
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
You could convince upstream to fall back on .xscreensaver if /apps
/gnome-screensaver is empty.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
thats a good idea but sadly not as easy to implement as it sounds, you'd
need to patch gconf very intursively to achieve that
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
We could also have gnome-screensaver do that. We don't need to patch gconf at
all.
William knows about xscreensaver and likely wants his application to replace it.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
still i think g-s-s rather should go on using gconf, so either a script
or an g-s-s code enhancement is needed to transfer the ~/.xscreensaver
settings into gconf, other apps rely on the fact that gconf is used for
settings in gnome-screensaver
--
Settings lost during an upgrade
https://launchpad
That is exactly the right thing to do!
Here's some pseudocode:
1. Check if /apps/gnome-screensaver has entries
2. If yes, carry on.
3. If no, look for .xscreensaver. If you find that, import as many entries as
you can into /apps/gnome-screensaver.
That's a total win for everybody.
--
Settings
yup i totally agree and thats what i meant above with "its trivial", but
would you do it with a permanent wrapper or with a hack to g-s-s ? i
think both is suboptimal ... but what sucks least ?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
deskt
The solution with the least suckage is to get it in the gnome-screensaver
binary. That way, all distributions win, instead of us keeping around a
non-standard patch.
Anyway, it's not a hack. It's a migration tool. :)
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desk
touching user settings in a postinst of a package is a big nono
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case, my primary screensaver is "None" (blank screen). How hard
would it be to check for at least this case?
also, re: "touching user settings in a postinst of a package is a big
nono." While my settings may not have been touched in actuality, they
were effectively touched because I upgrad
I guess this bug can be closed because Breezy is not supported anymore
and I think hardly anyone is upgrading from Breezy to Dapper anymore.
This bug doesn't exist in later releases, please report if it does by
any chance.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Inval
Doing a migration could be rather tricky.
What do you think, guys? Converting X resources to gconf keys?
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
only some lines (3-5) of the ~/.xscreensaver file would be needed, converting
that would be trivial, but the way *how* to implement it is a bit tricky, i
dont want a permantent wrapper script around the screensaver daemon...
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31
I guess this bug can be closed because Breezy is not supported anymore
and I think hardly anyone is upgrading from Breezy to Dapper anymore.
This bug doesn't exist in later releases, please report if it does by
any chance.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Inval
My screensaver settings were lost as well.
Breezy - Dapper upgraded through dist-upgrade 10 minutes ago...Note that
mid-install, I noticed that it paused because it said that configuration files
were changed... (didn't write down which ones, although I should have).
I chose the packager'
there is no relation between xscreensaver and gnome-screensaver settings
(thats exactly what this bug is about) conffile prompts on package
upgrades are unrelated here.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (Ubuntu)
Status: Unconfirmed => Confirmed
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
You could convince upstream to fall back on .xscreensaver if /apps
/gnome-screensaver is empty.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
thats a good idea but sadly not as easy to implement as it sounds, you'd
need to patch gconf very intursively to achieve that
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
We could also have gnome-screensaver do that. We don't need to patch gconf at
all.
William knows about xscreensaver and likely wants his application to replace it.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
still i think g-s-s rather should go on using gconf, so either a script
or an g-s-s code enhancement is needed to transfer the ~/.xscreensaver
settings into gconf, other apps rely on the fact that gconf is used for
settings in gnome-screensaver
--
Settings lost during an upgrade
https://launchpad
That is exactly the right thing to do!
Here's some pseudocode:
1. Check if /apps/gnome-screensaver has entries
2. If yes, carry on.
3. If no, look for .xscreensaver. If you find that, import as many entries as
you can into /apps/gnome-screensaver.
That's a total win for everybody.
--
Settings
yup i totally agree and thats what i meant above with "its trivial", but
would you do it with a permanent wrapper or with a hack to g-s-s ? i
think both is suboptimal ... but what sucks least ?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
deskt
The solution with the least suckage is to get it in the gnome-screensaver
binary. That way, all distributions win, instead of us keeping around a
non-standard patch.
Anyway, it's not a hack. It's a migration tool. :)
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desk
touching user settings in a postinst of a package is a big nono
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case, my primary screensaver is "None" (blank screen). How hard
would it be to check for at least this case?
also, re: "touching user settings in a postinst of a package is a big
nono." While my settings may not have been touched in actuality, they
were effectively touched because I upgrad
I guess this bug can be closed because Breezy is not supported anymore
and I think hardly anyone is upgrading from Breezy to Dapper anymore.
This bug doesn't exist in later releases, please report if it does by
any chance.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Inval
My screensaver settings were lost as well.
Breezy - Dapper upgraded through dist-upgrade 10 minutes ago...Note that
mid-install, I noticed that it paused because it said that configuration files
were changed... (didn't write down which ones, although I should have).
I chose the packager'
there is no relation between xscreensaver and gnome-screensaver settings
(thats exactly what this bug is about) conffile prompts on package
upgrades are unrelated here.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (Ubuntu)
Status: Unconfirmed => Confirmed
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
You could convince upstream to fall back on .xscreensaver if /apps
/gnome-screensaver is empty.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
thats a good idea but sadly not as easy to implement as it sounds, you'd
need to patch gconf very intursively to achieve that
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
We could also have gnome-screensaver do that. We don't need to patch gconf at
all.
William knows about xscreensaver and likely wants his application to replace it.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
still i think g-s-s rather should go on using gconf, so either a script
or an g-s-s code enhancement is needed to transfer the ~/.xscreensaver
settings into gconf, other apps rely on the fact that gconf is used for
settings in gnome-screensaver
--
Settings lost during an upgrade
https://launchpad
That is exactly the right thing to do!
Here's some pseudocode:
1. Check if /apps/gnome-screensaver has entries
2. If yes, carry on.
3. If no, look for .xscreensaver. If you find that, import as many entries as
you can into /apps/gnome-screensaver.
That's a total win for everybody.
--
Settings
yup i totally agree and thats what i meant above with "its trivial", but
would you do it with a permanent wrapper or with a hack to g-s-s ? i
think both is suboptimal ... but what sucks least ?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
deskt
The solution with the least suckage is to get it in the gnome-screensaver
binary. That way, all distributions win, instead of us keeping around a
non-standard patch.
Anyway, it's not a hack. It's a migration tool. :)
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desk
touching user settings in a postinst of a package is a big nono
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case, my primary screensaver is "None" (blank screen). How hard
would it be to check for at least this case?
also, re: "touching user settings in a postinst of a package is a big
nono." While my settings may not have been touched in actuality, they
were effectively touched because I upgrad
Doing a migration could be rather tricky.
What do you think, guys? Converting X resources to gconf keys?
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
only some lines (3-5) of the ~/.xscreensaver file would be needed, converting
that would be trivial, but the way *how* to implement it is a bit tricky, i
dont want a permantent wrapper script around the screensaver daemon...
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31
My screensaver settings were lost as well.
Breezy - Dapper upgraded through dist-upgrade 10 minutes ago...Note that
mid-install, I noticed that it paused because it said that configuration files
were changed... (didn't write down which ones, although I should have).
I chose the packager'
there is no relation between xscreensaver and gnome-screensaver settings
(thats exactly what this bug is about) conffile prompts on package
upgrades are unrelated here.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (Ubuntu)
Status: Unconfirmed => Confirmed
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
You could convince upstream to fall back on .xscreensaver if /apps
/gnome-screensaver is empty.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
thats a good idea but sadly not as easy to implement as it sounds, you'd
need to patch gconf very intursively to achieve that
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
We could also have gnome-screensaver do that. We don't need to patch gconf at
all.
William knows about xscreensaver and likely wants his application to replace it.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
still i think g-s-s rather should go on using gconf, so either a script
or an g-s-s code enhancement is needed to transfer the ~/.xscreensaver
settings into gconf, other apps rely on the fact that gconf is used for
settings in gnome-screensaver
--
Settings lost during an upgrade
https://launchpad
That is exactly the right thing to do!
Here's some pseudocode:
1. Check if /apps/gnome-screensaver has entries
2. If yes, carry on.
3. If no, look for .xscreensaver. If you find that, import as many entries as
you can into /apps/gnome-screensaver.
That's a total win for everybody.
--
Settings
yup i totally agree and thats what i meant above with "its trivial", but
would you do it with a permanent wrapper or with a hack to g-s-s ? i
think both is suboptimal ... but what sucks least ?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
deskt
The solution with the least suckage is to get it in the gnome-screensaver
binary. That way, all distributions win, instead of us keeping around a
non-standard patch.
Anyway, it's not a hack. It's a migration tool. :)
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desk
touching user settings in a postinst of a package is a big nono
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case, my primary screensaver is "None" (blank screen). How hard
would it be to check for at least this case?
also, re: "touching user settings in a postinst of a package is a big
nono." While my settings may not have been touched in actuality, they
were effectively touched because I upgrad
Doing a migration could be rather tricky.
What do you think, guys? Converting X resources to gconf keys?
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
only some lines (3-5) of the ~/.xscreensaver file would be needed, converting
that would be trivial, but the way *how* to implement it is a bit tricky, i
dont want a permantent wrapper script around the screensaver daemon...
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31
I guess this bug can be closed because Breezy is not supported anymore
and I think hardly anyone is upgrading from Breezy to Dapper anymore.
This bug doesn't exist in later releases, please report if it does by
any chance.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Inval
My screensaver settings were lost as well.
Breezy - Dapper upgraded through dist-upgrade 10 minutes ago...Note that
mid-install, I noticed that it paused because it said that configuration files
were changed... (didn't write down which ones, although I should have).
I chose the packager'
there is no relation between xscreensaver and gnome-screensaver settings
(thats exactly what this bug is about) conffile prompts on package
upgrades are unrelated here.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (Ubuntu)
Status: Unconfirmed => Confirmed
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
You could convince upstream to fall back on .xscreensaver if /apps
/gnome-screensaver is empty.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
thats a good idea but sadly not as easy to implement as it sounds, you'd
need to patch gconf very intursively to achieve that
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
We could also have gnome-screensaver do that. We don't need to patch gconf at
all.
William knows about xscreensaver and likely wants his application to replace it.
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
still i think g-s-s rather should go on using gconf, so either a script
or an g-s-s code enhancement is needed to transfer the ~/.xscreensaver
settings into gconf, other apps rely on the fact that gconf is used for
settings in gnome-screensaver
--
Settings lost during an upgrade
https://launchpad
That is exactly the right thing to do!
Here's some pseudocode:
1. Check if /apps/gnome-screensaver has entries
2. If yes, carry on.
3. If no, look for .xscreensaver. If you find that, import as many entries as
you can into /apps/gnome-screensaver.
That's a total win for everybody.
--
Settings
yup i totally agree and thats what i meant above with "its trivial", but
would you do it with a permanent wrapper or with a hack to g-s-s ? i
think both is suboptimal ... but what sucks least ?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
deskt
The solution with the least suckage is to get it in the gnome-screensaver
binary. That way, all distributions win, instead of us keeping around a
non-standard patch.
Anyway, it's not a hack. It's a migration tool. :)
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desk
touching user settings in a postinst of a package is a big nono
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case, my primary screensaver is "None" (blank screen). How hard
would it be to check for at least this case?
also, re: "touching user settings in a postinst of a package is a big
nono." While my settings may not have been touched in actuality, they
were effectively touched because I upgrad
Doing a migration could be rather tricky.
What do you think, guys? Converting X resources to gconf keys?
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
only some lines (3-5) of the ~/.xscreensaver file would be needed, converting
that would be trivial, but the way *how* to implement it is a bit tricky, i
dont want a permantent wrapper script around the screensaver daemon...
--
Settings lost during an upgrade
https://launchpad.net/malone/bugs/31
I guess this bug can be closed because Breezy is not supported anymore
and I think hardly anyone is upgrading from Breezy to Dapper anymore.
This bug doesn't exist in later releases, please report if it does by
any chance.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Inval
One-time job in the postinst?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
One-time job in the postinst?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
One-time job in the postinst?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
One-time job in the postinst?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
One-time job in the postinst?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
One-time job in the postinst?
--
Settings lost during an upgrade
https://launchpad.net/bugs/31511
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
96 matches
Mail list logo
