Bug#836136: new note crash related to tidy
Thanks for the report! This is essentially the same issue as in #834031. On 2016-08-30 23:21, Joey Hess wrote: > Package: pumpa > Version: 0.9.2-1+b1 > Severity: normal > > pumpa is crashing when I click on New Note > > pumpa: /build/tidy-html5-kAYBhq/tidy-html5-5.2.0/src/config.c:409: > prvTidySetOptionBool: Assertion `option_defs[ optId ].type == TidyBoolean' > failed. > Aborted > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages pumpa depends on: > ii libaspell15 0.60.7~20110707-3+b1 > ii libc6 2.23-5 > ii libgcc1 1:6.2.0-1 > ii libgl1-mesa-glx [libgl1] 11.2.2-1 > ii libqt5core5a 5.6.1+dfsg-3+b1 > ii libqt5dbus5 5.6.1+dfsg-3+b1 > ii libqt5gui55.6.1+dfsg-3+b1 > ii libqt5network55.6.1+dfsg-3+b1 > ii libqt5widgets55.6.1+dfsg-3+b1 > ii libstdc++66.2.0-1 > ii libtidy5 1:5.2.0-2 > > pumpa recommends no packages. > > pumpa suggests no packages. > > -- no debconf information > signature.asc Description: OpenPGP digital signature
Bug#834031: pumpa: Pumpa crashes when comment button is pressed.
Thanks for the report! The problem is related to the new version of libtidy in stretch not working in the same way as the old libtidy. I'll take a look at how to best fix it. Best regards, Mats On 2016-08-11 16:45, Timo Kankare wrote: > Package: pumpa > Version: 0.9.2-1+b1 > Severity: normal > > Dear Maintainer, > > I started Pumpa and pushed comment button on a post. Then Pumpa > crached. This seems to happen every time. > > Output in terminal was: > > $ LANG=en_US pumpa > Using locale "en_US" > Successfully loaded translation > libpng warning: iCCP: known incorrect sRGB profile > libpng warning: iCCP: known incorrect sRGB profile > libpng warning: iCCP: known incorrect sRGB profile > libpng warning: iCCP: known incorrect sRGB profile > pumpa: /build/tidy-html5-5.2.0/src/config.c:409: prvTidySetOptionBool: > Assertion `option_defs[ optId ].type == TidyBoolean' failed. > Keskeytetty > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages pumpa depends on: > ii libaspell15 0.60.7~20110707-3+b1 > ii libc6 2.23-4 > ii libgcc1 1:6.1.1-10 > ii libgl1-mesa-glx [libgl1] 11.2.2-1 > ii libqt5core5a 5.6.1+dfsg-3+b1 > ii libqt5dbus5 5.6.1+dfsg-3+b1 > ii libqt5gui55.6.1+dfsg-3+b1 > ii libqt5network55.6.1+dfsg-3+b1 > ii libqt5widgets55.6.1+dfsg-3+b1 > ii libstdc++66.1.1-10 > ii libtidy5 1:5.2.0-1.1 > > pumpa recommends no packages. > > pumpa suggests no packages. > > -- no debconf information > signature.asc Description: OpenPGP digital signature
Bug#781352: ssl cert fail causes pumpa to exit, deleting in-progress post
On Fri, Mar 27, 2015 at 05:07:16PM -0400, Joey Hess wrote: If I have a note I'm trying to post, and the current wifi network is a typical horrible gatewayed public wifi network, the post may fail a couple of times. I'll then go do something else. In the meantime, pumpa will try to refresh the timeline. Then pumpa will complain that it got a bad ssl cert. Then it will exit. This causes the words I was trying to post to get lost. I suggest pumpa not exit in this situation, but instead just fail whatever network operation is being blocked by the MITM. I'm glad someone is testing Pumpa in weird networking conditions, this is a situation that never occurred to me! Destroying the user's data not acceptable, I've put it as a high priority bug in the upstream bug tracker: https://pumpa.branchable.com/bugs/ssl_cert_fail_causes_pumpa_to_exit__44___deleting_in-progress_post/ Best regards, Mats -- Mats Sjöberg - http://sjoberg.fi/ OpenPGP key: 8A9F94D8, http://sjoberg.fi/publickey.asc Email encryption guide: https://emailselfdefense.fsf.org/ signature.asc Description: Digital signature
Bug#734477: more info
On Fri, 11 Jul 2014 13:19:50 -0400 Joey Hess jo...@debian.org wrote: I suspect there are multiple failure modes here. Two I have seen: 1. Progress bar stalls with bottom bar displaying network error, as described earlier. Maybe this is just some temporary network problem. I believe the real problem is that subsequent attempts consistently fail. 2. Posting immediately fails. Retrying also fails. Moving to a very fast and good network and retrying then also fails. In this case I had to completely restart pumpa for it to be able to post. This problem I was able to reproduce, in fact the problem was worse than you suspected: after one aborted upload (regardless of network problems), any further uploads will fail. This was simply due to a failure to reset the status of the upload. I have fixed this now in the most recent git commit: https://gitorious.org/pumpa/pumpa/commit/e253e05844b1443c4e84e8e39010fcc24f9dee45 Best regards, Mats -- Mats Sjöberg - http://sjoberg.fi/ OpenPGP key: 8A9F94D8, http://sjoberg.fi/publickey.asc Email encryption guide: https://emailselfdefense.fsf.org/ pgp4C3Ee24NVZ.pgp Description: PGP signature
Bug#737081: seems to miss displaying some comments to posts
Mats Sjöberg wrote: Another partial solution would be to reload the inbox feed itself, which usually contains the 20-or-so newest posts. This would automatically get the 4-5 newest comments for each of those posts. Right now Pumpa only polls for new items. In the most recent git master version Pumpa now reloads the full inbox timeline (or 200 most recent posts if you are showing more than that, this is a limit of the API). This should at least in theory get the 4-5 most recent comments of everything in the inbox with a single HTTP request. I think this is the best I can do in a client. I guess I can mark this bug as resolved once I make the 0.9 release and it has entered Debian. Best regards, Mats -- Mats Sjöberg - http://sjoberg.fi/ OpenPGP key: 8A9F94D8, http://sjoberg.fi/publickey.asc Email encryption guide: https://emailselfdefense.fsf.org/ pgpJFF1V6muEc.pgp Description: PGP signature
Bug#744800: double posts comments
On Mon, Apr 14, 2014 at 04:13:07PM -0400, Joey Hess wrote: pumpa sometimes double-posts comments. I'm using an identi.ca account. I have mostly seen this on dialup, but just observed it while on broadband. Clicked post and the dialog box wet away and came back less than 1 second later. Reloaded the timeline on a whim and saw my comment had gotten through, so posting again would have been a double post. I assume this is a protocol error, such as the server accepting the submissing, but hanging up before it tells the client it went through. I haven't seen this bug myself. But I'm mostly using my own pump.io instance. Maybe identi.ca has a higher load or something triggering the bug more often. It could be protocol error, but a quick look at the code in Pumpa didn't make me 100% sure it isn't a bug in my code... I'll have to look deeper into this when I get the time. signature.asc Description: Digital signature
Bug#737081: seems to miss displaying some comments to posts
On Wed, Jan 29, 2014 at 07:44:15PM -0400, Joey Hess wrote: https://microca.st/howcanuhavemyusername/note/U3BdE1SYRpmcDl-_5Ae6WQ In the web interface, this post has 4 comments. In pumpa, only the first comment is shown. (After expanding the post in the UI since it started collapsed.) I noticed several other posts where pumpa was not showing some or all of the comments. Tried reloading the timeline in pumpa, this did not make the missing comments show up. Restarting pumpa entirely did. Yes, I'm pretty sure I know why this problem occurs, but I haven't yet decided on the best solution. My guess is you are not following the other people in who replied to the thread (whose replies did not show up in Pumpa)? The problem is that Pumpa currently fills in any new replies (that appear after the main post has first appeared) when they arrive in the meanwhile feed. The meanwhile feed shows only replies from people you follow. To get all replies it would have to reload the original post, but the problem is I cannot know which posts have received new replies, so I would have to poll *all* posts in the inbox, which would cause something like 20-100 extra http requests. Another partial solution would be to reload the inbox feed itself, which usually contains the 20-or-so newest posts. This would automatically get the 4-5 newest comments for each of those posts. Right now Pumpa only polls for new items. Anyway, I will need to figure out some kind of solution before the next release, this is an annoying issue. Regards, Mats signature.asc Description: Digital signature
Bug#734477: Acknowledgement (image upload consistently fails on dialup)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Jan 07, 2014 at 11:54:37AM -0400, Joey Hess wrote: Same problem on quite fast and good broadband. Very strange, since it works fine for me (I just tested it). From your description it sounds like it is the actual file upload POST request that fails for some reason. Are you able to catch the exact error message, it should include some error id's and the URL it fails on: Network or authorisation error [%1/%2] %3. where %1, %2 are numbers and %3 the URL that it failed on. The error message should also show up in stdout, which is probably easier to catch than from the GUI status bar. (BTW as this is my first package in Debian I'm a bit unsure what is the usual/proper policy with regard to keeping bugs reported here and bugs in the upstream bug tracker in sync. The upstream is here: https://bugs.saz.im/pumpa but I might move it once gitorious gets a bug tracker.) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJSzDQSAAoJEC2v53YkWW4RxSEIAIgQq7pVCBJDntpNiX81cX9f 2xjUpufBtczIaL0yYTongWJEul6JMkZFWxc2s+ZKmLTS77T8dxep2p1AXQXgmF7O xd6qRXk/OE03AW8NehH0z0KAX0dn2vP3hte6KHMb5lwacmVpchjT+V2ySXc8mzZ5 AiK4YF2aI85jqhItoS5dXqfN5bCvqBjvaZ5DXReSOnQVq0LIAmrn7frXNNmdL/Jz a/QnQbno3LhLmvk5WAN73V6eJdJ4+rfMZickuBa4RBX0Qb8V59c9ezMxuiuG4HA4 nmus2wPpDKz5v+SQF1ejmK7Zh6U5n1UgwBPEGl7v0zriF6v4bIDpvrtVKQzW1KM= =MnCt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732657: RFS: pumpa/0.8.1 [ITP] -- a new pump.io/identi.ca client
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package pumpa, I'm also the upstream author * Package name: pumpa Version : 0.8.1 Upstream Author : Mats Sjöberg m...@sjoberg.fi * URL : http://saz.im/software/pumpa.html * License : GPLv3+ Section : net It builds the binary package: pumpa - simple desktop client for pump.io, the distributed social network To access further information about this package, please visit the following URL: http://mentors.debian.net/package/pumpa Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/pumpa/pumpa_0.8.1.dsc The upstream git repo has all the debian packaging as well: git clone git://gitorious.org/pumpa/pumpa.git More information about pumpa can be obtained from http://saz.im/software/pumpa.html - it was also mentioned in a recent LWN article: https://lwn.net/Articles/575691/ and many users have request a Debian package. Regards, Mats Sjöberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
