Arkisto, elokuu 2020

This hasn’t manifested itself in ages anymore, so it’s probably fixed

30. elokuuta 2020 klo 16.36
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Mattermost

This hasn’t manifested itself in ages anymore, so it’s probably fixed.

Vastaa viestiin sen kontekstissa (Github)

Mobile devices receive ghost notifications for already read messages

29. elokuuta 2020 klo 20.07
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, LineageOS, Mattermost, Samsung

Summary

Mobile devices receive ”ghost” notifications for already read messages, when set to receive notifications ”when Away or offline”, and receiving user is set to be Away.

Steps to reproduce

  1. Set ”Mobile Push Notifications” to ”Trigger push notifications when”: ”Away or offline” (and send ”For all activity”)
  2. Using web interface on desktop, set your status to Away
  3. (Still in the web interface) receive a message in the currently open channel (which immediately marks it read)

Expected behavior

Nothing happens on the mobile device (no notification).

Observed behavior (that appears unintentional)

The mobile device receives a notification about the already read message. The notification immediately disappears. If you weren’t looking at the device, you’re left wondering why it alerted you.

Other info

If your status is set to Online instead of Away (at step 2), the mobile device receives no notification (as expected). If ”Trigger push notifications when” is set to ”Online, away or offline” (at step 1), the mobile device receives no notification irrespective of your Online/Away status (also as expected).

Environment Information

I’m self-hosting Mattermost 5.26.1 with self-hosted MMPNS 5.22.4. Mattermost Mobile is at version 1.34.0. My mobile devices have Android 10 (Samsung) and Android 7.1.2 (LineageOS 14.1).

I don’t know if this is an issue with the client or the server; I can re-report against the latter if appropriate.

Vastaa viestiin sen kontekstissa (Github)

Updated client to 3.0.1 and the issue persists

29. elokuuta 2020 klo 9.51
Sijainti: Vianhallintajärjestelmät: Nextcloud

Updated client to 3.0.1 and the issue persists.

Vastaa viestiin sen kontekstissa (Nextcloud)

Can’t open main dialog

28. elokuuta 2020 klo 20.06
Sijainti: Vianhallintajärjestelmät: Nextcloud

Expected behaviour

Selecting ”open main dialog” from the client menu brings up the main dialog.

Actual behaviour

Selecting ”open main dialog” from the client menu either does not bring up the main dialog, or brings it up only to have it disappear almost immediately. The location of the main dialog, when it does pop up, also seems random: sometimes it pops up in the top left corner of the scereen, sometimes at the center of the screen, sometimes right where the tray menu is.

If I’m quick enough to bring the mouse cursor over the main dialog when it pops up, the window seems to stay, until I take the cursor out of it, at which point the window disappears.

The settings window does still open as normal when selected, and works without issues.

Steps to reproduce

  1. Select ”open main dialog” from the client (”tray”) menu

Client configuration

Client version: 3.0.0-20200821.171045.ff175088a-1.0~focal1

Operating system: Ubuntu 20.04, Wayland

OS language: Finnish

Qt version used by client package (Linux only, see also Settings dialog): Don’t know where to find that. The settings dialog only says ”Version 3.0.0 (Ubuntu)” AFAICT.

Client package (From Nextcloud or distro) (Linux only): Don’t understand the question.

Installation path of client: /usr/bin/nextcloud

Logs

The client debug log from the time of trying to open the main dialog shows this:

2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]:  screenRect: QRect(0,0 2560x1440)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]:  taskbarRect: QRect(0,0 2560x32)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]:  taskbarScreenEdge: OCC::Systray::TaskBarPosition::Top
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]:  trayIconCenter: QPoint(73,507)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]:        taskbarScreenEdge: OCC::Systray::TaskBarPosition::Top
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]:        screenRect: QRect(0,0 2560x1440)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]:        windowRect (reference) QRect(-127,36 401x511)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]:        windowRect (adjusted ) QRect(4,36 401x511)
2020-08-28 19:50:04:859 [ warning default ]:    qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:861 [ warning default ]:    qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:863 [ warning default ]:    qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:865 [ warning default ]:    qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:868 [ info nextcloud.sync.accessmanager ]:  2 "" "https://(MY SERVER URL)/ocs/v2.php/apps/notifications/api/v2/notifications?format=json" has X-Request-ID "b0e242bb-588d-455f-a53d-066d8d0b9f42"
2020-08-28 19:50:04:868 [ debug nextcloud.sync.cookiejar ]      [ OCC::CookieJar::cookiesForUrl ]:      (REDACTED)
2020-08-28 19:50:04:869 [ info nextcloud.sync.networkjob ]:     OCC::JsonApiJob created for "https://(MY SERVER URL)" + "ocs/v2.php/apps/notifications/api/v2/notifications" "OCC::ServerNotificationHandler"
2020-08-28 19:50:04:886 [ warning default ]:    qrc:/qml/src/gui/tray/Window.qml:473:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]:    qrc:/qml/src/gui/tray/Window.qml:496:17: QML Image: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]:    qrc:/qml/src/gui/tray/Window.qml:510:17: QML Column: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]:    qrc:/qml/src/gui/tray/Window.qml:547:17: QML Button: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]:    qrc:/qml/src/gui/tray/Window.qml:487: ReferenceError: hovered is not defined

Meanwhile, in syslog from the time:

Aug 28 19:50:04 saegusa gnome-shell[4105]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4200016 specified for 0x4200014.
Aug 28 19:50:31 saegusa gnome-shell[4105]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4200016 specified for 0x4200014.
Aug 28 19:50:35 saegusa gnome-shell[4105]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4200016 specified for 0x4200014.
Aug 28 19:50:47 saegusa kernel: [17841.949249] nextcloud[55212]: segfault at ffffffffffffffff ip 00007f2b3b765671 sp 00007ffe18796c78 error 5 in libgobject-2.0.so.0.6400.3[7f2b3b737000+36000]
Aug 28 19:50:47 saegusa kernel: [17841.949258] Code: b5 2c 02 00 48 8b 34 d8 eb b6 66 66 2e 0f 1f 84 00 00

Vastaa viestiin sen kontekstissa (Nextcloud)

Feature request: different highlight for already pushed commits in interactive rebase

19. elokuuta 2020 klo 16.29
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Git, Vim

Having shot myself in the foot by rewriting already pushed history, it occurred to me that perhaps I could have the commits list in interactive rebase reflect the commits’ push status in color. If lines of commits that I’ve already pushed to a remote were colored red (or any sufficiently differentiating color), I might actually notice when I’m about to screw up again.

To illustrate what I mean, here’s a mockup I made. This is what it would look like if this was my commit history, and 8b0ce7b was the last commit I had already pushed to a remote:

Kuvakaappaus 2020-08-19 15-52-35

I have no previous experience in modifying syntax highlighting code, and I have no idea if what I’m suggesting is even possible with vim, so I figured I’d open this request first in case it’s a silly idea, or conversely, if you deem this useful enough to implement yourself.

Vastaa viestiin sen kontekstissa (Github)

Currently experiencing this

15. elokuuta 2020 klo 18.32
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Ubuntu

Currently experiencing this. `lsof /var/lib/dpkg/lock` shows only ”focal” as holding the lock. The same ”focal” process is also eating up all of the CPU. No dpkg or apt processes are listed by `ps` either.

Vastaa viestiin sen kontekstissa (Launchpad)

Löysin samanlaisen sulan viime viikolla, ja parviäly tunnisti sen lehtokurpan sulaksi

8. elokuuta 2020 klo 21.25
Sijainti: Blogit: Luontoa ja puutarhaa Hankoniemellä

Löysin samanlaisen sulan viime viikolla, ja parviäly tunnisti sen lehtokurpan sulaksi.

Vastaa viestiin sen kontekstissa (Luontoa ja puutarhaa Hankoniemellä)