Lol, I did run the correct command yesterday and got the same error message. Sorry to ask a dumb question. I have a /var/crash/_usr_bin_pkexec.0.crash and I get a "permission denied" when I try to report a problem with it. Can it be attached to a bug report ? I cannot open it. I'll look Edit : Code: -rw-rw---- 1 root whoopsie 0 mars 14 22:03 .lock -rw-r----- 1 root whoopsie 330947 mars 14 22:29 _usr_bin_pkexec.0.crash
-rw-rw---- 1 root whoopsie 0 mars 14 22:03 .lock -rw-r----- 1 root whoopsie 330947 mars 14 22:29 _usr_bin_pkexec.0.crash
Last edited by bapoumba; March 14th, 2014 at 10:36 PM.
| My old and mostly abandoned blog | Linux user #413984 ; Ubuntu user #178 J'aime les fraises. Nighty night me lovelies! | SSO registration guide | Ubuntu Membership via forums contributions || Reinstalling Ubuntu ? Please check this bug first ! | | Using a ppa ? Please install ppa-purge from universe, you may need it should you want to revert packages back | | No support requests / username changes by PM, thanks. | [SIGPIC][/SIGPIC]
You could open it as root, but I wouldn't bother as it will not help you much, being mainly CoreDump: base64 H4sICAAAAAAC/0NvcmVEdW1wAA== 7H0LfFNF1vhtKXh5CEGqJqWrUQGL0JJCilVQUnlY5BWhaJFHE9 q0CbRJSNJSEDUuPuqqbFTU+o7vuvotUaBT31FQ6+qudUW3Pvbb +NzuimtdX7g++j/nztzcyc2zKH5+37/p73Rm7pw5c2bmzPvMzEVzF87LysoS5F+OMEiQXUZB+RkFvVAbx RGEL0YofvfkCzE/KbwBwJ8jSh80ACZBGMzskj+4hTDnr6F0o/5mgK5Y/yG8vwVAr2X+ORLE+LvhW2/Vbj68wPv7MTYL9Rf8EsSE918C/yIsfLYEMf6By8D+3u5oonsPj6WP/r19yeMPXob/25PGHxwChp/6GwZJEOPfNTRLMGxtj8bfNSKWPvq7W9uTxh8Bf39r8vgjV4C/lkTDh1Tl1wv+Bh1JWn7Cb7IEU6x/DH0N+Js5/6CKvh78e1PQN4C/kJecvgn8NZy/OSuWvhn8LWOT07eAv3tscvpu8Pczf4nfBP5BLrxblT4/8pefPP4A+Ovzk8cfBH8D89cniD+M+ZufPP4u8A+niD8C/l0p4u8F/0gKf+FKKD/O36DKfw34649R8k8tn+hvOCY5f3rwNx2TPH4D+JuPSV4+6O/mwgvZqvYJ/fXJ4zeDv1+fPH4L+Af0MemL8w9y4f2q/HFj/hyfPH4/5s/xyeMPYP5w/gZV+QcxfSnohzB9KeiHMX2cf1gtX5j/J6SQL/C3nJBCvpC/FP7CVcAf5991tEq+wN88I4V8gb9lRkz9iW1fkP6MFO0L+AdS+J vBP8j5hwfF8mfB+Gclzx83+LtnJafvR/44f7Mq/wPg35WCfhD8Iynoh8C/d1Zy+QmDv96UnH4X+BtMyelHwN/E+QdU8t+L/Jel6F+uBv7LUvQv4N/L/EMUYuUX/INncPHnqeQX/A2rk8sP+ptWJ5efXvC3rE4hv9ugfJm/gUJs+wT+wdXJ2wcT+OurUrRP4G+oStE+gb+pKnn/4Qd/Cxc+oJYv8O9NEX8Q/AVLCvkCfw3nH1SlLwz+IWsK+QL/sDWFfIF/F+cf1KjkC/Pfk0K+fgv1y5NCvsA/kMJfD/5Bzh9ij4nfgP4bk8dvAv/QxhTtC/iHOf8uVflYkL/mFO0Lxt+con3B9G9S5N+t7n/Av3dTcvkJgr9mcwz9GP5C4K/fnLz/DaP/lhTlD/6GLSnKH/m75GnKX7YEsv9gKs4S3uwlS+fS0lF+vP26w0ASAK4EaDwsdp4T HCXE/1BmmNxkM8hhXuczwN80gD74DdtVS7xgnweI7v0XtZ/P8bAFYBDHY/YcoFVjMvUM6hl0jYov93pbs61aYYO69VMavZ4p3rUO5xTvJqfV 7XNU64WD+g1ms4T5Z85fps4zv/A/8xtMpw1Suco8YfJyczeT46Sy3kxQNPq+vfIwuexHg1HD8tUI89 McFgZpDQWQihjkUmRx4Lc5v88Rh4PZA4Hkae/hzD2SmUczedIBzPjmsqePBXP/qMufRhFZAG6e51Xwce7C+fNknhdG23iY78pzYjRh/jtIYPPgCOVVmpPJ8y40YY41TGovwA7zqeFS2wB2ee4kmXlkqOS A+RDMiSR8nBvJ8x80Ya5zpCQ4YId5zVGSgIM9OkcBE+YjUj7iv ATmHlJe4RxDnkeg2cVwcO4QYTg4D5DH+mjCuH6MxD/YTcyOY3kYr+dKPIBdHnujCePsY6W0gx3G1JII49hZHh+jCWPho yWaYIdxr1aiCXZ5jIsmjGezJTpgh7GrlLc4hpXHqWjCmFTKQxy bwvhTKm8cZ8pjSTRh3HgBFjaOH/3MjmNFGA9ehHYc98ljOzRhHDdD4gHsMGabKdEEuzw+QxPGYlJ9 wjEZjLukPMTxlzzGQhPGUxL/OK6CsZPEP46h5HESmjAmktKOYyMY/+ikvIJxjjyWQRPGLQ8gnzh+sTA7jlVgPPKgxD/Y5bEFmjCOoHkLdhgzSPRxbCD3/5JpYXUG+nTo1yV5w/5d7sPRhP5a4gf7beib8ySewS73w27adg7NYu0o9K/DJH7ALveVaEK and such-like. However, if you right click on that file it should offer you the chance to open it with "Report a problem"
Code-tags --- Boot-Repair --- Grub2 wiki & Grub2 Basics --- RootSudo --- Wireless-Info --- SolvedThreads --- System-Info-Script
Yes, but as I stated above, I get a "permission denied" when I try to report a problem. I'll attach a screenshot.
For root owned .crash files either open /var/crash in a root browser or try from terminal in various ways - Code: sudo /usr/bin/apport-cli /path/to/whatever.crash or maybe Code: gksudo /usr/share/apport/apport-gtk /path/to/whatever.crash
sudo /usr/bin/apport-cli /path/to/whatever.crash
gksudo /usr/share/apport/apport-gtk /path/to/whatever.crash
Thanks mc4man, first one did it. I promise I looked how to get around the permission denied as the file was not owned by me, but could not find anything to use. https://bugs.launchpad.net/ubuntu/+s...1/+bug/1292722 It says the bug contains private information.
Last edited by bapoumba; March 14th, 2014 at 11:16 PM.
Originally Posted by bapoumba https://bugs.launchpad.net/ubuntu/+s...1/+bug/1292722 It says the bug contains private information. all bug reports from crashers thru appoprt are 'private' until someone removes possible personal info (a bug triager Myself wait for a retrace & then if after a day or two if not looked at or duped generally mark as public as there is nothing on my testing install that could be compromising or whatever. Sometimes apport crash reports contain useful info to debug, sometimes not..
Well, I had a look at the files, and there was no real private info I could see. But I'm not that well trained I cannot make it public myself. I linked to the previous bug in a comment. We shall see, thanks again!
Originally Posted by bapoumba I cannot make it public myself. If you get inclined at some point you should be able to. On bug pages any yellow circle can be clicked on for an action or more. see screens as example (I've no private bugs atm so picked latest open one Certainly no harm in waiting either..
OK thanks, I can indeed mark it public. I can wait too (Sorry, I have not filed bugs and used LP in a long while).
The bug ajgreeny reported has been marked as a duplicate of this one, which has been marked as fix released : https://bugs.launchpad.net/ubuntu/+s...n/+bug/1292868. lxsession is at the proper version here, but opening synaptic with gtk-launch synaptic still brings up the same error here (all updates applied). Using the menu item or the launcher icon still does not work. I wonder if ajgreeny's bug really is a duplicate..
View Tag Cloud
Ubuntu Forums Code of Conduct