New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installed styles have been purged #278

Closed
saxamaphone69 opened this Issue Dec 3, 2017 · 63 comments

Comments

Projects
None yet
@saxamaphone69

saxamaphone69 commented Dec 3, 2017

  • Browser: Chrome 62
  • Operating System: Windows 10
  • Stylus Version: 1.1.7.2
  • Screenshot:

stylus-blank

Woke up this morning to find all my styles missing. Entering this into the console did not bring them back, and attempting to export/checking the IndexedDB, provided an empty json file.

I can create a new style and it appears.

@saxamaphone69 saxamaphone69 changed the title from Stylus to Installed styles have been purged Dec 3, 2017

@tophf

This comment has been minimized.

Member

tophf commented Dec 3, 2017

Do you see the style objects in devtools -> Application -> IndexedDB?

pic

@saxamaphone69

This comment has been minimized.

saxamaphone69 commented Dec 3, 2017

That's where I looked, and it's completely empty.

@tophf

This comment has been minimized.

Member

tophf commented Dec 3, 2017

I don't know how to reproduce this bug so I'm not sure if it's caused by Stylus, and not by Chrome.

@saxamaphone69

This comment has been minimized.

saxamaphone69 commented Dec 3, 2017

Not sure either. Chrome hasn't updated overnight, but Stylus did.

If it helps, I did not have any of my userstyles using the new user.css format - I didn't even know it existed until I started trying to find out the issue.

@tophf

This comment has been minimized.

Member

tophf commented Dec 3, 2017

The thing is, there's simply no code in Stylus that deletes the styles without explicit user action for one style at a time.

The only guess I have, is that for some reason IndexedDB didn't work so Stylus saved all styles in chrome.storage, which you can view using Storage Area Explorer extension or by running the following code in devtools opened on any Stylus page:

chrome.storage.local.get(null, console.log)

Click the output to expand it and see if the styles are there.

@saxamaphone69

This comment has been minimized.

saxamaphone69 commented Dec 3, 2017

stylusstorage

Nope. Dang, looks like I just got unlucky then. Strange, never had an issue and have been using Stylus since the fork from Stylish, and have been thoroughly enjoying the updates. That should teach me to update my style without pushing the changes to GitHub!

@tophf tophf added the external label Dec 6, 2017

@tophf

This comment has been minimized.

Member

tophf commented Dec 6, 2017

Looks like something happened to the browser profile and corrupted IndexedDB.
I'll see if I can implement "timemachine" that would backup the styles from IndexedDB into another type of storage and allow rolling back.

@saxamaphone69

This comment has been minimized.

saxamaphone69 commented Jan 1, 2018

This just happened again. Latest Chrome and latest stable release (63, 1.1.8).

Chrome open, editing my style as usual. Made a change to a line, go to save to see the results, but the button refuses to press. I try the keyboard shortcut. Still refuses to change. I open up the console on the Stylus page, no errors reported. I go to close the editing window, but the alert/popup saying I have unsaved changes pops up. I click Stay. I then try going back to manage. Same popup. I try deleting the line I had just changed, no luck. Still no errors or warnings in the console. I then just leave the page anyway and close the tab I was working on, just in case. I open it back up and everything seems normal, but I still can't make changes. I try creating a new userstyle and it never appears in the manage page. I close Chrome, open it up, and all my styles have been wiped again, but this time the userstyle I tried creating which wouldn't appear just earlier is there. I've checked the IndexedDB and it has the key path id 9, so that means it knows it's the 9th style, but the previous 8 aren't there.

I know that doesn't reduce the test case, but this time it occurred while Chrome was still running and I attempted to save, but it refused to let me save. I'll muck around now and see if I can get it happening again.

@tophf

This comment has been minimized.

Member

tophf commented Jan 2, 2018

Still sounds like a bug in the browser or a broken user profile. Like I said, Stylus simply doesn't have code to mass-delete styles except when you manually import a json in the manager and then press the undo button to roll back the import, in which case the imported styles are deleted and the old styles are restored.

P.S. I'm keeping this issue "open" only as a reminder to myself about the "timemachine" feature, not as an invitation to provide more details about the bug. There's nothing we can do about it because it's definitely not caused by our code.

@tophf

This comment has been minimized.

Member

tophf commented Jan 15, 2018

Another user found out the culprit was CCleaner.
Make sure to exclude "HTML5 storage" or just everything browser-related.

@cubedj

This comment has been minimized.

cubedj commented Jan 15, 2018

that's exactly why I'm not using CCleaner... a realy long time ago it corrupted my Windows registry so many times I had to do inplace upgrade every half year until I finally found out and ditched that bitch and I never had to reinstall Windows again ever since... nevertheless this kind of bug happened to me a few times as well and every time it was because the db in userprofile has been corrupted (probably by Chrome itself) in a way that Stylus was able to read from it but when trying to save - the data was never written despite the fact there was no exeption thrown both from Stylus and Chrome.. in fact Chrome sometimes does the completely same thing with its own settings... it trained me to export the Styles quite often but the rollback feature would be fine ;)

@MarkRH

This comment has been minimized.

MarkRH commented Feb 11, 2018

I'm on Firefox 58.0.2 and Stylus 1.2.7 and I somehow lost all my styles after either clicking on Manage (and not really doing anything) or possibly after clearing parts of History that managed to wipe what Stylus had saved as well. Luckily I had a stylus.json file available to re-import. Perhaps I will try and re-create.

Should going to History -> Clear all History wipe out Stylus if say everything is checked?

@tophf

This comment has been minimized.

Member

tophf commented Feb 11, 2018

I think Firefox may consider IndexedDB inside WebExtensions a part of "site history" when clearing the data. It certainly seems retarded to me but some other apps do that as well e.g. CCleaner so this confusion may be a common thing.

@narcolepticinsomniac

This comment has been minimized.

Member

narcolepticinsomniac commented Feb 11, 2018

Should going to History -> Clear all History wipe out Stylus if say everything is checked?

Is this still an issue? I thought it was pretty well sorted out now. Been a while since I've seen it reported.

Make sure you haven't hidden them on yourself before you reinstall:
#145 (comment)

Otherwise, keep frequent backups. "Re-create" makes it sound much more dramatic than what the process actually is. Uninstall/reinstall/import, takes less than a minute.

@MarkRH

This comment has been minimized.

MarkRH commented Feb 11, 2018

All those filters were unchecked. Anyway, already imported what I had saved. By re-create I meant making them all go poof again to see what actually caused it.

Well, I tried to make it happen again be selecting everything in Clear Recent History but my styles remained intact. So, I dunno.

@TayliaM

This comment has been minimized.

TayliaM commented Feb 12, 2018

I tried reproducing @MarkRH's FF losing styles issue last night. (Firefox 58.0.2/Stylus 1.2.7) Didn't appear to be having any luck but this morning when I opened the browser my styles were all gone. Haven't been able to reproduce again yet, but I'll keep playing with it some.

@tophf

This comment has been minimized.

Member

tophf commented Feb 12, 2018

I'll remind just in case that setting Firefox to "Never remember history" in its options will switch style storage in Stylus to chrome.storage API instead of IndexedDB i.e. the first time you enable that option all your previously saved styles will be inaccessible (effectively, gone) because Firefox won't allow Stylus to use IndexedDB. Subsequent toggling of the option won't switch the storage back to IndexedDB because Stylus will keep using chrome.storage API.

@TayliaM

This comment has been minimized.

TayliaM commented Feb 12, 2018

Good to know. Thank you.

@BoffinbraiN

This comment has been minimized.

BoffinbraiN commented Apr 3, 2018

I can also confirm I lost everything after running CCleaner to clean up HTML5 storage (in this case, for Firefox). After restoring the contents of my firefox\profiles\profilename\storage directories from a backup, everything returned. I won't be doing that again!

@ripdog

This comment has been minimized.

ripdog commented May 1, 2018

I just lost all my styles after a FF Nightly update, and I don't use CCleaner.

Aaaand I just installed a style, it appeared in the open Stylus management tab, but didn't apply to the site. I reload the Stylus tab and the style disappeared. Hmm. This has happened repeatedly. I'd suspect a nightly bug, but no other addons have lost settings.

It seems that Stylus is broken until reinstall in this version: http://forums.mozillazine.org/viewtopic.php?f=23&t=3040021

You need to restart Nightly after uninstalling Stylish.

@tophf

This comment has been minimized.

Member

tophf commented May 2, 2018

It seems that Stylus is broken until reinstall in this version: http://forums.mozillazine.org/viewtopic.php?f=23&t=3040021

AFAIK there's nothing in Stylus that could possibly trigger this kind of bug in FF Nightly. I've seen many nonsensical bugs in FF Nightly over the last year so that must be just another one.

@myfonj

This comment has been minimized.

myfonj commented May 2, 2018

Nightly, lost all styles today as well.
In my case I had some application crash prior observed purge.

@TayliaM

This comment has been minimized.

TayliaM commented May 2, 2018

I'll remind just in case that setting Firefox to "Never remember history" in its options will switch style storage in Stylus to chrome.storage API instead of IndexedDB i.e. the first time you enable that option all your previously saved styles will be inaccessible (effectively, gone) because Firefox won't allow Stylus to use IndexedDB. Subsequent toggling of the option won't switch the storage back to IndexedDB because Stylus will keep using chrome.storage API.

Has the toggling behavior changed? My nightly didn't lose any styles with "Remember history", but when switching to "Never remember history" they were gone, as I guessed they would be. Installed a couple there. Switching back and forth, I have two sets of styles being accessed.

@elypter

This comment has been minimized.

elypter commented May 16, 2018

i have had similar problems with other firefox addons for several times now. i assumed it is a file system problem because i am running my system from an usb stick with a lose connection and crash it several tiems a day usually. if it happens on both chrome and firefox it might be some javascript framework related issue

@GuyXY

This comment has been minimized.

GuyXY commented Jun 4, 2018

I have a pretty similar problem. I'm using Firefox 60.0.1 on Windows 7 (in case this is somehow relevant)
My installed styles are not listed anymore and when I click on "find styles", nothing happens.
I've checked if the add-on's storage file is corrupted and I'm not 100% sure. The storage file in my profile folder is 917 KB large and all the payload fields contain what looks like a bunch of Chinese characters. The json structure seems so be valid. I've got no errors when I tried to pretty print it.

I hope there's some other way to fix that than installing every single style from scratch again. I've had quite a few of them.

@Zero3

This comment has been minimized.

Zero3 commented Jun 11, 2018

I just lost my styles as well :(. What happened to me:

  1. Opened Chrome monday morning. Stylus is deactivated. Instead, there is a new toolbar button for updating Chrome (the one that appears when you haven't restarted Chrome for ages and Chrome wants you to restart it to apply updates).

  2. I click the update button and Chrome restarts. Stylus is still not working.

  3. I visit the extensions page in Chrome, and Stylus is marked as corrupted and has a "repair" button.

  4. I click the repair button which triggers a fresh install of Stylus. My styles are still missing :(.

@narcolepticinsomniac

This comment has been minimized.

Member

narcolepticinsomniac commented Jun 11, 2018

@Zero3 This repo is for "Stylus", which is a fork of the original "Stylish" for Chrome. We are a completely different extension. You're either confusing the spelling, or more likely, you're in the wrong place.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 25, 2018

I used Stylish for years, and never encountered this problem. I've used Stylus since February.

I believe Zero3 is probably correct - the number of people who actually report a problem here are only ever a tiny fraction of the people who experience it.

I'm also a programmer, but I'm not familiar with your source code.

I'm aware of the location of my profile folder. What I was asking was where, in that folder, would the database have been kept?

I back up my profile folder, but I don't do it as a rolling backup to separate folders - each one overwrites the previous one. I last made a backup on the 22nd, which may or may not help, and I also back that folder up to Dropbox, once in a while, which may or may not offer previous versions -
but without knowing which file to restore, I'm not going to get very far.

I would have thought your FAQ covered this. I don't understand what you've said so far. So, the file name could be anything long and obscure? I see nothing like that, when I open the style manager, or the editor.

@Mottie

This comment has been minimized.

Member

Mottie commented Aug 25, 2018

The WebExtension API in Firefox, and likely Waterfox, is not fully matured. So, comparing the history of a non-WebExtension version of Stylish with the WebExtension version of Stylus isn't valid.

I don't know about Waterfox, but Firefox stores the extension database in the same place for all extensions. I can only tell you where it can be found in Windows 10:

C:\Users\{user}\AppData\Roaming\Mozilla\Firefox\Profiles\{?}.default-{?}\storage\default\moz-extension+++19f1eea9-d818-427e-bdfc-e48d4e08c83c\idb

The 19f1eea9... is the ID of Stylus set by addons.mozilla.org, so you may see something different. You can find this id in the browser URL after opening the manager or editor.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 25, 2018

Thanks, Mottie, but the FAQ does just that - part of it refers to Stylus; part of it refers to Stylish. No part of it explains how to restore a backup of the database, as far as I can see.

Apparently I now have Stylus 1.4.20. I don't see any indication of whether or not it's a web extension.

I see three possible candidates for the folder, in C:\Users{me}\AppData\Roaming\Waterfox\Profiles{?}.default\storage\default but I don't know if that applies, or how to tell which.

@Mottie

This comment has been minimized.

Member

Mottie commented Aug 25, 2018

Only WebExtensions will work in Firefox v57+, I don't know what version of Waterfox that applies to. Open the Stylus manager and look for the ID in the URL.

In Firefox it's moz-extension://19f1eea9-d818-427e-bdfc-e48d4e08c83c/manage.html

@Andy2No

This comment has been minimized.

Andy2No commented Aug 25, 2018

Okay. Thanks, Mottie. I hadn't realised I was supposed to be looking for that in the URL.

It seems I don't have a useful backup, and neither does Dropbox. I do still have the styles backed up from Stylish, in February, so I can at least go back to that.

@narcolepticinsomniac

This comment has been minimized.

Member

narcolepticinsomniac commented Aug 25, 2018

@Zero3 The flaw in those speculative stats is that they fail to take into account the severity of the issue. To stick with a "bug" analogy, the percentage of people who'll avoid going to the doctor for a common cold is probably comparable to the percentage of users who won't bother reporting minor bugs. Complete DB failure is more like organ failure, so baseline stats of normal bug reporting wouldn't really apply the same.

@Andy2No The majority of reports here either have to do with external file-cleaners or FF in general, with a few unexplained Chromium failures. Only reason I'm chiming in, is that it might be worth mentioning that FF has a fallback DB due to the ongoing bug in FF where privacy settings are applied to WebExtension storage. IndexedDB is faster, so that's what is used, but if you change FF to "never remember history" or any other strict privacy settings/configs, it'll fall back to an inferior storage which isn't affected. Unfortunately, the two are completely independent, so you can't switch back and forth, it's either one or the other. Changing privacy settings could cause Stylus to use the fallback, making it appear that all styles have been purged, when in reality, simply undoing the strict privacy settings will allow Stylus to access the default DB again.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 25, 2018

That's interesting, narcolepticinsomniac, but I don't use any extreme privacy settings, and haven't changed them in quite a while.

I've restored my styles from the database for Stylish (reverting back to February), by using this tool to convert them to a format Stylus could import from:

https://www.jeffersonscher.com/res/stylishextract.html

FWIW, if I'd been able to find anything useful in the FAQ, I wouldn't have reported the problem either.

@Mottie

This comment has been minimized.

Member

Mottie commented Aug 25, 2018

The FAQ is a wiki page, if you feel something is lacking, please help us out and update and/or share more detailed information.

@narcolepticinsomniac

This comment has been minimized.

Member

narcolepticinsomniac commented Aug 25, 2018

I can empathize with the frustration. I've lost many hours of coding before due to DB loss. In my case, it's always been user error, because I tend to constantly be testing different versions. I've "uninstalled" the wrong one more times than I care to admit. It's gotten to be second nature to click the export button most times I see it.

FWIW, if you're sticking it out with FF 56, you should probably be using the legacy Stylish 2.1.1. One of the main reasons users stick with old versions of FF is so they can still use the much more powerful XUL based extensions. The legacy Stylish has much more control over the entire browser than any WebExtension ever could. If I was using any pre-v57 FF, I certainly wouldn't use a WebExtension like Stylus.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 25, 2018

@Mottie, I'll give some though to adding to the FAQ when I've recovered a bit from the frustration.

I don't know how long the tool from https://www.jeffersonscher.com/res/stylishextract.html will stay available though, so I don't know whether to refer to that or not. It's the only way of doing it that I've found, other than reinstalling Stylish to export its database, which may or may not still work, due to version changes.

@narcolepticinsomniac, I'm currently using Waterfox 56.0.4.1 (64-bit), but I'm not sure how the version numbers work. I assume that means it's based on FF 56, but I've never really looked into it. As I see it, I have to eventually put up with WebExtensions, or stop using FF based browsers all together.

@narcolepticinsomniac

This comment has been minimized.

Member

narcolepticinsomniac commented Aug 25, 2018

AFAIK, one of Waterfox's main objectives is to continue support for XUL based extensions. If you like it, and plan on sticking with it, you should really stick to the more powerful legacy Stylish.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 26, 2018

I'll give that some thought, narcolepticinsomniac. I can't remember why I switched to Stylus, though it made sense at the time.

I have read that there are/were privacy concerns about Stylish - selling data about users. How much truth there is in that, I don't know. I don't think that was the reason I switched though. On the whole, Stylus seems to do enough, for what I need it for.

@stonecrusher

This comment has been minimized.

Contributor

stonecrusher commented Aug 27, 2018

The FAQ is a mix of bits about Stylus and Stylish. I can't currently make any sense of that, i.e. I don't know which parts of it apply.

Please read carefully and distinguish between Stylus, Stylish < 3.0.1 and Stylish >= 3.0.1.
Actually the faq are pretty clear on this. Exporting from Stylish, importing to Stylus.
There are no instructions or mentions for fiddling around with Stylus' database, not even where to find it.

Your question "Restore Stylus database from old FF profile which already used Stylus" is a different one. Though the recommended way is to backup your styles regularly via the export function found on Stylus' manage page. Maybe we could add a weekly automatic export into the profile folder up to a limited number of backups? @tophf

I don't know how long the tool from https://www.jeffersonscher.com/res/stylishextract.html will stay available though, so I don't know whether to refer to that or not.

Jefferson is a very reliable person. I don't think you have to worry about the page going offline soon. On the other hand it is licensed under BSD-3-Clause which allows redistribution, so there's also the possibility to selfhost a copy of it on github pages or something.

It's the only way of doing it that I've found, other than reinstalling Stylish to export its database, which may or may not still work, due to version changes.

This makes no sense. Stylish 3.0.1 or higher doesn't even have a stylish.sqlite anymore and there is an export function available. So if you restored a stylish.sqlite with Jefferson's tool, then it was an even older leftover version from before using Stylish 3.0.1.
The only described and recommended way for exporting styles from Stylish 3.0.1 or higher is to use the internal export function.
Jefferson's tool's only purpose is to convert a database from Stylish < 3.0.1 to a format which can be imported into Stylus. No more.

There is no info about reinstalling Stylish>=3.0.1 for export because no one tested yet if the styles are kept forever if you uninstall Stylish. If that is the case, I can add it.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 28, 2018

I'm not sure where to start, with all that, stonecrusher. As I said, I eventually restored my database from Stylish, from February, using Jefferson's tool.

I appreciate that needing to do that is a minority interest. It works though. I'm not sure which version of Stylish I was using at the time. I also said I wasn't sure if reinstalling Stylish to get its contents would be practical. I'm not sure why that "makes no sense". It either works, or it doesn't. If I had the correct version of Stylish installed, I should be able to recover the styles somehow - e.g by copying and pasting.

I suspect the FAQ seems clearer to you than it does to the people who feel the need to read it. I'm not sure how it helps to keep information there that relates to Stylish, or earlier versions. People reading an FAQ want to know things about the current version. Talking about older versions, or the ancestor of this extension, just makes it confusing to read.

I was attempting to restore the database from a backup of my Waterfox profile, yes. To do that, I needed to know where it was. I now know from this discussion, but not from the FAQ.

As it turned out, I didn't have a backup that was old enough, but otherwise, that would have worked. There was no "fiddling with databases" involved - I just wanted my database back, from a few days earlier.

An automatic export seems like a really good idea, but documenting how to use a backup of a profile would be useful too. I back up folders, with SyncBackSE. I don't necessarily know everything about the contents - the FF/Waterfox profile contains a lot that's mysterious to me. I don't necessarily want to restore an entire folder from a backup, because I'd be overwriting something else that I might have needed.

Getting back to Jefferson's import tool - it probably isn't still needed by many people, so arguably doesn't belong in the FAQ. It is a useful resource though, so it would be good if it could be preserved in more than one place.

I used it to migrate to Stylus originally, and I've now used it again, to import the exact same data. There will be other people who find they need to, but yes, a fairly small minority.

@stonecrusher

This comment has been minimized.

Contributor

stonecrusher commented Aug 28, 2018

We can have a chat on discord if you want.
It is just important to know from where you are starting.

I don't necessarily want to restore an entire folder from a backup, because I'd be overwriting something else that I might have needed.

That's why an automatic Stylus backup would be helpful instead of restoring a whole IndexedDB which might also contain other information or may be easily deleted / corrupted by the browser.

People reading an FAQ want to know things about the current version. Talking about older versions, or the ancestor of this extension, just makes it confusing to read.

There are people who come from older versions because they used ESR versions or browser forks where newer extension versions are not available. Or they simply liked the old Stylish much better for its power to change the browser UI, so stayed as long as possible. Another issue was that Stylish botched the change to webextensions so we have the need to fetch the user whereever he started.

I just wanted my database back, from a few days earlier.

So you were already coming from Stylus? Please be clear on that.
Then that export-import question in our faq is completely unrelated to what you wanted. Maybe helpful for further steps, but actually you want to find Stylus' DB.

Maybe something like C:\Users\[username]\AppData\Roaming\Mozilla\Firefox\Profiles\[profile.name]\storage\default\moz-extension+++[StylusExtensionUUID]\idb\489858440shtsyil.sqlite as mentioned above by Mottie.

@Andy2No

This comment has been minimized.

Andy2No commented Aug 28, 2018

Yes, I migrated from Stylish to Stylus in February, stonecrusher. My first post in this thread was about having lost my styles, in Stylus and wanting to know what I could do about it, after trying to find out from the FAQ... I thought that was fairly clear, but maybe not.

As I see it, I was trying to get my lost styles back. If I'd exported them, importing them would have been an option, but I hadn't - and hadn't thought to, so I was looking to restore them from a backup.

I guess you could see it as two different things. I see it as two different approaches to the same problem - winding the clock back to when I had it how I wanted it.

I found myself trying to restore from a backup and having no information available to tell me how. I guess you could argue that situation isn't frequent enough to qualify as an FAQ, but it's a pretty short list, at the moment, and I really don't think I'm the only person who's ever going to want to know that.

If I had exported them, I'd probably already know what to do about it to get them back (i.e., I personally would know, and probably so would most other people) so I wouldn't have been needing to look at the FAQ.

I feel I've identified something that could usefully be added to the FAQ. Of course, it's up to you to decide whether or not it should be there.

The information to do it has been given in this thread, and I feel I could now add it myself, if that helps, but maybe it would be better coming from someone who understands the whole picture better... on the other hand, there are a lot of good manual writers who know very little about the technicalities, they're just good at explaining how to use something, which is what the readers / users actually need. Good programmers aren't always the best communicators, in my experience.

@MarjaE2

This comment has been minimized.

MarjaE2 commented Sep 7, 2018

Nightly, lost everything including custom safety tools.

@MarjaE2

This comment has been minimized.

MarjaE2 commented Sep 7, 2018

Are there any files to recover?

@vsemozhetbyt

This comment has been minimized.

vsemozhetbyt commented Oct 27, 2018

Maybe ssomething like this can help in cases like this or #528:

https://github.com/gruns/irondb

@DeathTBO

This comment has been minimized.

DeathTBO commented Nov 6, 2018

It's happened to me a few times after recently switching from Stylish to Stylus.

On a side note, is it supposed to take a long time to load my styles after a reboot? Usually 1-2 minutes and then my styles are loaded.

@eight04

This comment has been minimized.

Collaborator

eight04 commented Nov 7, 2018

On a side note, is it supposed to take a long time to load my styles after a reboot? Usually 1-2 minutes and then my styles are loaded.

Definitely not. You may want to open a new issue for it.

@KingDGrizzle

This comment has been minimized.

KingDGrizzle commented Nov 7, 2018

I'm going to chime in on this issue, as I've just booted my PC and my styles were gone..

I opened the Dev Tools in the Manage Style page, only to notice this error: Error Image

Accessing BG.cachedStyles revealed that the list property had three values, all set to null.. (And mutex.inProgress set to true, whatever that means)

Now I know I should take backups of my styles, which I will do after I manage to re-configure them again, but this is a bit annoying to deal with... Either Chrome is being dumb, or there is some bug somewhere. I don't use CCleaner, nor clear my history (which seemed to be two main causes of this issue)

@eight04

This comment has been minimized.

Collaborator

eight04 commented Nov 7, 2018

I guess you just hit this bug: #528. You should be able to get your styles backup after another update (if you didn't reset your database).

@eight04

This comment has been minimized.

Collaborator

eight04 commented Nov 7, 2018

This issue is staled and reports are mixed with different browsers and different versions. I'm going to close this thread and open another one to discuss ironDB (or something similar).

@patrickdrd

This comment has been minimized.

patrickdrd commented Nov 12, 2018

I've just installed on the weekend on chrome and I've lost my styles twice already,
the most recent some minutes ago when I copied the whole chrome installation (portable)
to the work pc and of course styles weren't included (as they should be of course),
luckily for me I use firefox mostly so I exported and imported,
so that's not a big problem for me,
but the problem is that there's a problem

@narcolepticinsomniac

This comment has been minimized.

Member

narcolepticinsomniac commented Nov 12, 2018

This issue's closed, and I'm locking it. It does no good to have a single, ancient catch-all issue for DB failure where users complain without bothering to provide any helpful details.

@patrickdrd I would guess you're using Canary, because we've had reports recently through the last few versions. It's a browser bug which will supposedly be fixed in an upcoming update.

If you are using Canary, feel free to respond in that issue, although it's closed because it's not a bug in Stylus. If your issue is something else, please open a new issue with all relevant details to repro.

I copied the whole chrome installation (portable) to the work pc and of course styles weren't included (as they should be of course)

In almost all cases, that isn't the way it works anymore. Chrome/Chromium and the vast majority of its forks haven't been truly portable in quite a while. Most so-called "portable" installs still have extension settings locked to the device they're installed on, so they aren't transferable to another computer.

the problem is that there's a problem

So meta. Are you sick and tired of being sick and tired? =)

@openstyles openstyles locked and limited conversation to collaborators Nov 12, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.