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/
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.
@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.
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
Yes, this is still reproducible here with the current server (v5.29.1).
Here’s the server log and MPNS log during which
- I switch log level from error to debug
- I send one ”hello” message to a bot (from the web UI)
- the bot responds with one message
- I switch log level from debug back to error
- VSCode Version: 1.53.0
- OS Version: Ubuntu Linux 20.04
Steps to Reproduce:
- install .deb package
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
@@ -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
# Update mimetype database to pickup workspace mimetype
if hash update-mime-database 2>/dev/null; then
All right, looks like this is VSCode issue #37762 (and MD5 usage is #99760).
$ md5sum --quiet -c /var/lib/dpkg/info/codium.md5sums
md5sum: WARNING: 2 computed checksums did NOT match
$ apt-cache policy codium
*** 1.51.1-1605141118 500
500 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium/main amd64 Packages