Arkisto 2020

Yes, this is still present in 20.04

26. joulukuuta 2020 klo 16.56
Sijainti: Vianhallintajärjestelmät: Launchpad

Yes, this is still present in 20.04 with printer-driver-cups-pdf 3.0.1-6, limited to original reporter’s case of having the symlink point to another filesystem; if I point ~/PDF to, say ~/tmp/PDF (without crossing filesystem borders), the PDF is created without issue, whereas having ~/PDF linked to /media/$USER/$USB_THUMBDRIVE/PDF/ does still cause it to fail:

[…]
Sat Dec 26 16:48:07 2020 [DEBUG] output filename created: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf
Sat Dec 26 16:48:07 2020 [DEBUG] ghostscript commandline built: /usr/bin/gs -q -dCompatibilityLevel=1.2 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile=”/home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf” -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -c .setpdfwrite -f /var/spool/cups-pdf/SPOOL/cups2pdf-233705
Sat Dec 26 16:48:07 2020 [DEBUG] output file unlinked: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf
Sat Dec 26 16:48:07 2020 [DEBUG] TMPDIR set for GhostScript: /var/tmp
Sat Dec 26 16:48:07 2020 [DEBUG] waiting for child to exit
Sat Dec 26 16:48:07 2020 [DEBUG] entering child process
Sat Dec 26 16:48:07 2020 [DEBUG] GID set for current user
Sat Dec 26 16:48:07 2020 [DEBUG] supplementary groups set for current user
Sat Dec 26 16:48:07 2020 [DEBUG] UID set for current user: jani
Sat Dec 26 16:48:07 2020 [DEBUG] ghostscript has finished: 256
Sat Dec 26 16:48:07 2020 [ERROR] failed to set file mode for PDF file: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for…ry_342_200_-job_8.pdf (non fatal)
Sat Dec 26 16:48:07 2020 [DEBUG] ERRNO: 2 (No such file or directory)
Sat Dec 26 16:48:07 2020 [DEBUG] no postprocessing
Sat Dec 26 16:48:07 2020 [DEBUG] spoolfile unlinked: /var/spool/cups-pdf/SPOOL/cups2pdf-233705
Sat Dec 26 16:48:07 2020 [DEBUG] all memory has been freed
Sat Dec 26 16:48:07 2020 [STATUS] PDF creation successfully finished for jani
jani@latimeria:~$ ls -l PDF
lrwxrwxrwx 1 jani jani 27 joulu 26 16:47 PDF -> /media/jani/KINGSTON_1G/PDF
jani@latimeria:~$ ls -l PDF/
yhteensä 0

Vastaa viestiin sen kontekstissa (Launchpad)

I haven’t seen this since Ubuntu-distributed Firefox was updated to 84

20. joulukuuta 2020 klo 12.12
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Twitter, Ubuntu

For me this seems to have resolved itself since Ubuntu-distributed Firefox was updated to 84, though for all I know, it may have just coincided with some change implemented at Twitter’s end.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

I see, so it’s a result of conflicting indicators from the user

19. joulukuuta 2020 klo 18.41
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Mattermost, saavutettavuus

@agnivade Oh I see, so it’s a result of conflicting indicators (”away” vs. being active) from the user. I’m trying to recalibrate my expectation based on this, but it’s difficult.

My immediate thought is perhaps (in the problematic case) sending the notification, but then clearing it only once I start typing (typing appears to have an event associated with it, at least based on the logs) would be better than the immediately clearing ghost notification, but you’re right, this is more complicated than immediately apparent.

Some UI/UX design wizardry would probably be needed to eliminate the possibility of mixed user signals, if at all possible. I don’t have a good solution for now, so feel free to close the issue if you deem it appropriate.

Vastaa viestiin sen kontekstissa (Github)

Yup, your description of the issue is exactly right

18. joulukuuta 2020 klo 15.23
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Mattermost

Yup, your description of the issue is exactly right @agnivade, and thanks for looking into this!

I set up the two users in parallel windows. Sending a normal message as userB this way does not trigger the issue (I do get a notification on userA’s phone, but it doesn’t go away by itself), but that’s because userA’s window is (obviously) not active, since I’m typing in userB’s window. The notification is only cleared once I activate userA’s window.

But I can trigger the issue by using (for instance) /echo 'hello A' 4 instead (as userB), then hopping on to activate userA’s window during the 4-second delay, so that userA’s window is active when receiving the message. That’s the crucial bit: the receiver’s window is active when receiving the message. If his status is ’Online’, there’s no push notification (as expected), but if it’s ’Away’, that’s when I get the ghost notification.

Here’s server log and MPNS log during one minute where (as userB) I first send a normal message, then (at about 30 seconds) using /echo.

Vastaa viestiin sen kontekstissa (Github)

Still reproducible here with the current server (v5.29.1)

18. joulukuuta 2020 klo 10.26
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Mattermost

Yes, this is still reproducible here with the current server (v5.29.1).

Here’s the server log and MPNS log during which

  1. I switch log level from error to debug
  2. I send one ”hello” message to a bot (from the web UI)
  3. the bot responds with one message
  4. I switch log level from debug back to error

Vastaa viestiin sen kontekstissa (Github)

Twitter tabs don’t load in Firefox when set as home

13. joulukuuta 2020 klo 16.37
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Twitter, Ubuntu

I’m affected by this too, in Ubuntu 20.04 with Firefox 83.0+build2-0ubuntu0.20.04.1.

Tested nightly (85.0a1.en-US.linux-x86_64) with a clean profile, and the issue remains.

Steps to reproduce

  1. Start nightly with ./firefox -no-remote -profilemanager
  2. Create a new profile, select it and click Start Nightly
  3. Open these three tabs (replacing the first-run tabs currently open):
  1. Open preferences, set Home to Custom URLs…, select ”Use current pages”
  2. Close the window
  3. Start nightly again with ./firefox -no-remote -profilemanager, select the previously created profile

What happens

None of the three tabs load any content. The firefox process also doesn’t end after closing this window with the non-working tabs, I have to Ctrl-C out of it.

Further info

Upon subsequent starts, Nightly does appear to correctly load the tabs, whereas for my main Twitter profile and FF 83.0 no amount of restarts seems to help; instead I have to open another tab and open m.twitter.com in it, then click on the home button to have the home tabs load (and close the first, still stuck set of home tabs).

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Checksum mismatch in deb package for .desktop files

11. joulukuuta 2020 klo 19.45
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Debian, Ubuntu, VSCode

  • VSCode Version: 1.53.0
  • OS Version: Ubuntu Linux 20.04

Steps to Reproduce:

  1. install .deb package
  2. run debsums -s

Does this issue occur when all extensions are disabled?: Yes

I’d like to resurrect #37762: the checksums for .desktop files included in the .deb archive fail to pass post-install.

$ debsums -s code
debsums: changed file /usr/share/applications/code.desktop (from code package)
debsums: changed file /usr/share/applications/code-url-handler.desktop (from code package)

This happens because the postinst script calls desktop-file-install for the .desktop files, which adds an X-Desktop-File-Install-Version entry to them, and hence the checksums change.

I don’t know why the desktop-file-install call is there, as including the .desktop files in the deb archive is sufficient to have them installed (in their proper place under /usr/share/applications/), with the checksum intact.

I built the package with just those desktop-file-install calls removed (see below), after which the checksums pass post-install (with no other changes that I can see).

diff --git a/resources/linux/debian/postinst.template b/resources/linux/debian/postinst.template
index c72fe5f9f5..dcc147de93 100755
--- a/resources/linux/debian/postinst.template
+++ b/resources/linux/debian/postinst.template
@@ -12,12 +12,6 @@ ln -s /usr/share/@@NAME@@/bin/@@NAME@@ /usr/bin/@@NAME@@
 # developers would prefer a terminal editor as the default.
 update-alternatives --install /usr/bin/editor editor /usr/bin/@@NAME@@ 0
 
-# Install the desktop entry
-if hash desktop-file-install 2>/dev/null; then
-       desktop-file-install /usr/share/applications/@@NAME@@.desktop
-       desktop-file-install /usr/share/applications/@@NAME@@-url-handler.desktop
-fi
-
 # Update mimetype database to pickup workspace mimetype
 if hash update-mime-database 2>/dev/null; then
        update-mime-database /usr/share/mime

Vastaa viestiin sen kontekstissa (Github)

All right, looks like this is VSCode issue #37762 (and MD5 usage is #99760).

2. joulukuuta 2020 klo 18.14
Sijainti: Vianhallintajärjestelmät: Gitlab
Avainsanat: VSCode

All right, looks like this is VSCode issue #37762 (and MD5 usage is #99760).

Vastaa viestiin sen kontekstissa (Gitlab)

.desktop files’ checksums mismatch in deb package

2. joulukuuta 2020 klo 15.14
Sijainti: Vianhallintajärjestelmät: Gitlab

$ md5sum --quiet -c /var/lib/dpkg/info/codium.md5sums
usr/share/applications/codium-url-handler.desktop: FAILED
usr/share/applications/codium.desktop: FAILED
md5sum: WARNING: 2 computed checksums did NOT match

$ apt-cache policy codium
codium:
  Installed: 1.51.1-1605141118
  Candidate: 1.51.1-1605141118
  Version table:
 *** 1.51.1-1605141118 500
        500 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium/main amd64 Packages
        100 /var/lib/dpkg/status

Vastaa viestiin sen kontekstissa (Gitlab)

Capable for the price, but inseparably tied to cloud

30. marraskuuta 2020 klo 13.33
Sijainti: Muut: Amazon
Avainsanat: kuluttajuus

Given the price (less than 20 € when I bought mine) this is quite a capable little device. Physical manufacturing quality felt pretty good too.

Unfortunately the software is inseparably tied to manufacturer’s cloud service, and bypassing it for direct local access (such as RTSP) does not appear to be possible (not in a way that’s useful anyway). That’s the reason I ended up returning mine.

Vastaa viestiin sen kontekstissa (Amazon)

Vanhempia »