bert

joined 3 years ago
[–] bert@lemmy.monster 52 points 2 weeks ago (11 children)

Solid reporting in that final paragraph.

National Park Service workers were seen roping off the area Thursday afternoon, and National Guard members appeared to be directing the public away from the grass. National Park Service workers were seen later roping off the area.

[–] bert@lemmy.monster 2 points 5 months ago (4 children)

Looks like I can only see the three latest versions (as far back as 2.0.12). Is it user error or do I need to do something special to look further back?

[–] bert@lemmy.monster 9 points 1 year ago (1 children)

Put it in the Signal chat!

[–] bert@lemmy.monster 2 points 1 year ago* (last edited 1 year ago) (3 children)

Hmm, maybe I need to take another look through my settings (or perhaps I didn't clearly enunciate my issue), because when I click a thumbnail in my main feed it opens the link, rather than a larger version of the image.

I miss Sync for that singular feature of press+~~hole~~hold on a thumbnail in the feed to show a full size image of said thumbnail.

[–] bert@lemmy.monster 7 points 1 year ago (5 children)

Same here, though I do have one thing I miss from Sync: press+hold on an image in feed to make it full screen. Happen to know if there is a voyager setting to enable this functionality?

[–] bert@lemmy.monster 3 points 1 year ago

I approve of this message.

[–] bert@lemmy.monster 2 points 1 year ago (1 children)

That seems to have done the trick. Thank you!

[–] bert@lemmy.monster 2 points 1 year ago (1 children)

Thank you, all! No luck with any of these troubleshooting tips but it is good to know that I am not alone in my need to dismiss notifications.

 

Since the recent update I have had a red dot with a number 1 in it on top of my settings icon, as if to indicate a new feature or something. After looking through most of the options, the dot persists. Any ideas as to which menu I need to look into in order to clear the dot?

[–] bert@lemmy.monster 58 points 2 years ago (3 children)

the lawsuit is targeting three patents in particular. These primarily cover throwing an object in a specific direction to either summon a battle character or to capture a creature in the field

Better watch out, Ghostbusters. Your ghost trap might be next.

[–] bert@lemmy.monster 7 points 2 years ago

Does Ghostbusters count?

[–] bert@lemmy.monster 13 points 2 years ago (2 children)
 

After a migration to new hardware, I am receiving the following permissions error from Pict-rs.

The old hardware was using 991:991 and I did not catch it until after first run and the problem now persists after a chown -R 991:991 volumes/pictrs.

Can I salvage things? I'm not worried about saving any Pict-rs data, so I'd even go for some guidance as to the possibility of "resetting" Pict-rs.

lem-pictrs  |  Error: 
lem-pictrs  |     0: Error in database
lem-pictrs  |     1: IO error: Permission denied (os error 13)
lem-pictrs  |  
lem-pictrs  |  Location:
lem-pictrs  |     src/repo/sled.rs:84
lem-pictrs  |  
lem-pictrs  |    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lem-pictrs  |  
lem-pictrs  |     0: pict_rs::repo::sled::build with path="/mnt/sled-repo" cache_capacity=67108864 export_path="/mnt/exports"
lem-pictrs  |        at src/repo/sled.rs:78
lem-pictrs  |     1: pict_rs::repo::open with config=Sled(Sled { path: "/mnt/sled-repo", cache_capacity: 67108864, export_path: "/mnt/exports" })
lem-pictrs  |        at src/repo.rs:464
lem-pictrs  |  
lem-pictrs  |    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lem-pictrs  |    
lem-pictrs  |  
lem-pictrs  |  Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
view more: next ›