I noticed that the service is up locally during the (non-finishing) configuration phase, and produces journal log entries as usual, I’m attaching the relevant lines here. The gist of it appears to be an ”Error: no hostname or hostnames provided in connection string” from programs/server/node_modules/fibers/future.js:280

I’m unable to reproduce this snap issue in a VM, but so far I’ve failed to pinpoint the curcial difference between the VM and my physical server.

I’ve tried purging and reinstalling snapd, disabling IPv6, turning off Apache and any other services that might be in the way, rebuilding the snap with my previous settings built in but none of it has made any difference.

@xet7 Unfortunately the install now also fails with the same configure hook issue as refresh did:

root@battra:~# snap remove wekan
wekan removed
root@battra:~# snap install wekan
error: cannot perform the following tasks:
- Run configure hook of "wekan" snap if present (run hook "configure": )

(For mongodump, I had to replace/upgrade the Xenial package with mongodb-org-tools from the main MongoDB site, because Xenial’s mongodump 2.6 failed with assertion: 17369 Backing up users and roles is only supported for clusters with auth schema versions 1 or 3, found: 5. With mongodump 3.6.2 I was able to dump the db successfully.)

I came across this old Wekan snap report about the same issue. I enabled snap debugging as mentioned there, and will attach the result of grep snapd from during the installation attempt here.

Should I open a new issue about this, to keep this report on topic?

@xet7 When I try to refresh the snap, it gets stuck in Run configure hook of "wekan" snap if presentwith a node process eating up the CPU. It takes 5 minutes before snapd gives up. Now the service won’t come back up, and revert also fails:

root@battra:~# snap revert wekan
error: cannot perform the following tasks:
- Run configure hook of "wekan" snap if present (run hook "configure": )

For me the double slash regression occurred at 0.62-3-g74877fd (as it did for the reporter in #1405), whereas this edge-to-edge URL issue was already there in 0.60 (but the double slash issue wasn’t). It might not definitely make them completely unrelated, but would at least hint towards it.

Näytöntökkimäpelit tökkivät täälläkin. Ihmettelin jo silloin, kun olin hetken aikaa mobiilipelikoodarina, että miksei näille laitteille tehdyillä peleissä hyödynnetä laitteiden antureita. Pelisuunnittelussa yritetään vain mielikuvituksettomasti toisintaa vanhan maailman peliohjaimien fyysisiä nappeja siinä näytöllä, josta ei saa edes kunnon taktiilia palautetta.

Se kytkeytyy hyvin läheisesti pelien mekaniikkaan, eli pelit pitäisi nykyään alun alkaenkin suunnitella sellaisiksi, että niiden mekaniikan ohjaus soveltuisi luontevasti mobiililaitteen ominaisuuksilla tehttäväksi. Esimerkiksi perinteiset sidescrollerit ovat syntyneet joystickien ja painonappien ympäristössä, ja siksi niiden ohjaamiseen mobiililaitteella ei ole edes oikein mahdollista rakentaa painonappien simulointia luontevampia konsteja. Pitäisi siis luoda kokonaan uusia, mobiililaitteiden ohjaimille luontevia genrejä.

(En tuon lyhyen pelikoodarikeikkani jälkeen ole juurikaan seurannut mobiilipelien kehitystä, joten voi olla, että nykyään näin jo paremmin tehdäänkin.)

Impacted version: 0.60

Server Setup Information:

• Operating System: Ubuntu 16.04
• Deployment Method: snap
• ROOT_URL environment variable (Is there a subfolder?): https://my-domain.com/kan (yes)

Problem description:
A description consisting entirely of a URL that happens to extend from the left edge to the right edge of the description field makes it impossible to edit the description, as clicking anywhere on the viewer lands the click on the URL, which triggers a new browser tab instead of the editor.

Here’s a screenshot of such a URL overlapping the editing area, as highlighted by the inspector in Firefox.

There’s actually a couple of pixels worth of unlinked, clickable editor area at the right edge here, but you need a really steady hand and mouse to hit those pixels.

A workaround seems to be to change the browser zoom level (either way), causing the URL to extend either over to the next line or properly short of the right edge of the first line (turning the rest of the line clickable).

With WP_DEBUG enabled, a non-existing page (404) logs the following PHP error:

Trying to get property of non-object in wp-content/themes/cover2/components/header/header-overlay.php on line 53

I believe this is caused by the $post reference on that line, as $post has not been populated on a 404 page.

Mielenkiintoista nähdä kuinka sopeudut Mac-maailmaan, moni asia on siellä softapuolella toisin kuin Windowsissa. Laitepuolella perinteisesti laadukkaana pidetyn Applen ote on kuulemma tässä viime vuosina alkanut hieman lipsua, mutta sekin hyvä puoli (ilmeisesti) hieman vanhemman mallin valinnassasi on, että ilmestymisen jälkeen ensimmäisillä käyttäjillä ilmenneitä vikoja on niissä ehditty sittemmin tuotantolinjalla korjata.

Richardson mentioned that Lepsy smoked an obscure brand of cigarette, and that DB Cooper left a pack behind when he jumped off the plane. Does he know if Cooper’s cigarettes were of that same obscure brand?

Sorry if this was addressed in the episode and I just missed it.

After upgrading to Quantum, the right mouse button context menu for HTML links pops up in the wrong place when the Firefox window is pushed to either side of my screen (so that the window takes up half of the horizontal space). The issue appears similar to what has been reported in bug #1721614 (particularly as it appears in the video attached by the submitter), but for me the issue does not occur with the hamburger menu or other UI elements, only with links on webpages, and the menu highlighting behavior is different: in my issue the highlighting occurs normally only once I point the cursor at the menu.

== Steps to reproduce ==
1. Create a new profile and start Firefox using the profile.
2. Expand the window to fill the screen (if not already).
3. Enter search terms into the URL bar and hit enter to bring up a search results page.
4. Right-click a search result title to bring up the context menu. Left-click outside it to close it.
5. Grab the window title bar and push the window to the right edge of screen to resize the window to span half of screen horizontally. Release the title bar.
4. Right click the search result title again.

== What happens ==
The menu pops up on way off from where the mouse cursor is. See attached screenshot.

== What should happen ==
The context menu should pop up next to mouse cursor.

== Possible culprit ==
This seems to be somehow tied to localization: if I uninstall firefox-locale-*, then create a new Firefox profile, with this new profile the menu pops up where it should. I’m using Finnish locale, but this is reproducible with just firefox-local-en too, although the mispositioning differs between locales (Finnish pushes the menu off to the left, whereas English pushes it down and to the right).

== Workaround ==
Don’t right-click on the page before resizing the window (that is, skip step #4 above). This seems to be the trigger.

== Other info ==
I’m able reproduce this in a (16.04) VM just as well as on the host desktop.

In case the collected data doesn’t include this, my primary display is 2560 × 1440p, and the only display connected. xrandr output:

Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 2560×1440+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
2560×1440 59.95*+
2048×1152 59.90
1920×1200 59.88
1920×1080 60.00 50.00 59.94 24.00 23.98
1920x1080i 60.00 50.00 59.94
1600×1200 60.00
1680×1050 59.95
1280×1024 75.02 60.02
1280×800 59.81
1152×864 75.00
1280×720 60.00 50.00 59.94
1024×768 75.03 60.00
800×600 75.00 60.32
720×576 50.00
720×480 60.00 59.94
640×480 75.00 60.00 59.94
720×400 70.08
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

Screenshot with the context menu off to the left of mouse cursor (Finnish locale) Edit (490.3 KiB, image/png)