Arkisto, maaliskuu 2020

Their expressions on the freeze frame make it look like a poster for a romantic comedy

29. maaliskuuta 2020 klo 10.49
Sijainti: Videosivustot: YouTube

Their expressions on the freeze frame make it look like a poster for a romantic comedy ūüėĄ

Vastaa viestiin sen kontekstissa (YouTube)

For auto upload? I have Camera, OpenCamera and Screenshots

26. maaliskuuta 2020 klo 13.29
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Nextcloud

Folders for auto upload? I have Camera twice (/storage/emulated/0/DCIM/Camera; once for pictures, the other for videos), OpenCamera (/storage/emulated/0/DCIM/OpenCamera) and Screenshots (/storage/emulated/0/DCIM/Screenshots).

(I only tried OpenCamera briefly, recently, and have since uninstalled it. The issue at hand was present already back when I first got this phone and installed Nextcloud on it, last July.)

I’ve always had auto upload enabled until now, so can’t say whether it’s dependent on that. I could try disabling it next time the issue re-emerges; as dictated by Murphy’s law, I was unable to trigger it just now that I intentionally tried to.

Oh, and I am running Beta (so currently 3.11.0 RC4) of the Nextcloud app. Can’t remember when I enrolled in.

Vastaa viestiin sen kontekstissa (Github)

No instructions for updating (server) in README

25. maaliskuuta 2020 klo 17.34
Sijainti: Vianhallintajärjestelmät: Github

I presume updating an existing installation is just a matter of replacing the existing files with files from the new release, but as this isn’t made explicit in the readme, I’m just a bit apprehensive about going ahead with it.

Vastaa viestiin sen kontekstissa (Github)

Ctrl-v in comment field (rich editor) scrolls the view, hiding the card (when using Firefox)

24. maaliskuuta 2020 klo 10.48
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Chrome, Firefox, Wekan

Problem description
Using ctrl-v to paste content into a comment causes the view to scroll back horizontally so that if the card was already at the right edge of the view, it seemingly pops out of view. This happens when using Firefox; Chrome seems unaffected.

I’m currently unable to test whether the non-rich editor is affected due to¬†#2967, and also, as I was exclusively using non-rich editor prior to this, I can’t say if this occurred with the 3.85 refresh or whether it was here with the rich editor even before.

Server Setup Information

  • Wekan version: 3.85
  • Operating System: Ubuntu 16.04 (19.10 in another test VM)
  • Deployment Method: snap
  • What webbrowser version? Firefox 74.0, Chrome 80.0.3987.149

Logs contain nothing related to this AFAICT.

Steps to reproduce

  1. Copy something to clipboard
  2. Have a board with enough lists to fill the view horizontally, or contract the browser window to have one list at the right edge
  3. Open a card from the rightmost list
  4. Select the comment field, press ctrl-v

Demo
Here I’m first typing something, then pasting below it (using ctrl-v) to cause the unwanted scrolling to occur.

Peek 2020-03-24 10-08

Vastaa viestiin sen kontekstissa (Github)

Rich editor in place despite richer-card-comment-editor = false

24. maaliskuuta 2020 klo 10.32
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Chrome, Firefox, Wekan

After today’s snap refresh to 3.85, rich editor is used for comments despite¬†richer-card-comment-editor¬†being set to¬†false. Yesterday this was still working, and I didn’t change the settings, so it’s something to do with the latest refresh.

Server Setup Information:

  • Wekan version: 3.85
  • Operating System: Ubuntu 16.04 (19.10 in another test VM)
  • Deployment Method: snap
  • What webbrowser version? Firefox 74.0, Chrome 80.0.3987.149

Problem description:
(Nothing related in any logs)

screenshot

Vastaa viestiin sen kontekstissa (Github)

Confirming as fixed!

19. maaliskuuta 2020 klo 16.48
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Github, Gonimo

Confirming as fixed! (Sorry for not getting back sooner, looks like Github failed to notify me.)

Vastaa viestiin sen kontekstissa (Github)

Here’s output from logcat:

19. maaliskuuta 2020 klo 16.41
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Nextcloud

Here’s output from logcat:

03-19 16:33:47.099 20119 20119 E AndroidRuntime: FATAL EXCEPTION: main
03-19 16:33:47.099 20119 20119 E AndroidRuntime: Process: android.process.media, PID: 20119
03-19 16:33:47.099 20119 20119 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.android.providers.media.MediaScannerReceiver: java.lang.StringIndexOutOfBoundsException: length=1; index=-3
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.app.ActivityThread.handleReceiver(ActivityThread.java:3619)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.app.ActivityThread.access$1300(ActivityThread.java:237)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1803)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:214)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7078)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: Caused by: java.lang.StringIndexOutOfBoundsException: length=1; index=-3
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at java.lang.String.substring(String.java:1995)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at com.android.providers.media.utils.MPLogger.log(MPLogger.java:118)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at com.android.providers.media.MediaProvider.call(MediaProvider.java:5073)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.content.ContentProvider$Transport.call(ContentProvider.java:403)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.content.ContentResolver.call(ContentResolver.java:1763)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at com.android.providers.media.MediaScannerReceiver.logToDb(MediaScannerReceiver.java:139)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at com.android.providers.media.MediaScannerReceiver.onReceive(MediaScannerReceiver.java:77)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        at android.app.ActivityThread.handleReceiver(ActivityThread.java:3610)
03-19 16:33:47.099 20119 20119 E AndroidRuntime:        ... 8 more

The upload process (I think) then dies:

03-19 16:33:47.164  2044 13653 I ActivityManager: Killing 20133:com.nextcloud.client/u0a0 (adj 100): depends on provider com.android.providers.media/.MediaProvider in dying proc android.process.media (adj 100)

Vastaa viestiin sen kontekstissa (Github)

I have the same ”android.process.media has stopped” issue on my Samsung phone

19. maaliskuuta 2020 klo 16.28
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Nextcloud, Samsung

I have the same issue on my Samsung Galaxy A9 phone, with ”android.process.media has stopped” appearing for virtually every photo taken (though the uploads seem to still go through). My Samsung Galaxy Tab S5e does not have the same issue, nor do I recall seeing this on any other Android devices (from other manufacturers).

I don’t use alarmapp (to my knowledge, though I’m not sure which app that is).

Vastaa viestiin sen kontekstissa (Github)

You could release a RiffTrax-style ”Just the jokes” edit once the original stream is out there

17. maaliskuuta 2020 klo 20.19
Sijainti: Videosivustot: YouTube
Avainsanat: RiffTrax, tekij√§noikeus, YouTube

Came here to suggest just this: release a RiffTrax style ”Just the jokes” edit, to be played over the original stream once it’s out there.

Vastaa viestiin sen kontekstissa (YouTube)

Don’t show changelog after updating

17. maaliskuuta 2020 klo 12.30
Sijainti: Vianhallintajärjestelmät: Github

After starting Firefox today an unrequested ”What’s Updated” tab from HTTPS Everywhere (2020.3.16) popped up. I failed to find a way to prevent my workflow from being interrupted this way, so I had to resort to preventing automatic updates of the extension altogether.

Please don’t open unrequested tabs. I can find the changelog if I need to.

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »