[Bug 940631]
Fixed for me on 60.9.0+build1-0ubuntu0.18.04.1 according to apt policy thunderbird -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940631 Title: Thunderbird asks three times for my master password To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/940631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702407] [NEW] Update breaks chromium-browser on Ubuntu Mate 16.04.2
Public bug reported: $ apt-cache policy chromium-browser chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 0010 #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() #1 0x7f8cc1af580b #2 0x7f8cc1e20390 #3 0x5619ce286dc8 #4 0x5619ce289656 #5 0x5619ce289df9 #6 0x5619ce28a143 #7 0x7f8cc1b70821 #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f8cc1b2283d #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() #14 0x7f8cc1b49628 base::RunLoop::Run() #15 0x7f8cc1b75e36 base::Thread::ThreadMain() #16 0x7f8cc1b70726 #17 0x7f8cc1e166ba start_thread #18 0x7f8cab4c53dd clone r8: 002e r9: 5619cfcdd6ec r10: r11: 7f8cab552f50 r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 7f8c1b0d1eb0 di: si: 7f8c1b0d1eb0 bp: 7f8c1b0d1f00 bx: 7f8c1b0d1eb0 dx: 0061 ax: cx: 7f8bf0047070 sp: 7f8c1b0d1e60 ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Quits <1s after starting on desktop. Output from terminal-based launch is above. Worked earlier today before updating. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Update breaks chromium-browser on Ubuntu Mate 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702407] Re: Update breaks chromium-browser on Ubuntu Mate 16.04.2
This problem appears to be fixable by closing chromium and renaming ~/.config/chromium/ so a new set of config files is created by chromium when it is opened again. Then cp ~/.config/chromium_old/Default/Bookmarks ~/.config/chromium/Default/ This update introduced the new settings interface so perhaps something to do with that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Update breaks chromium-browser on Ubuntu Mate 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Update breaks chromium-browser on Ubuntu Mate 16.04.2
Sorry I didn't tell the whole story... close chromium $ sudo apt-get purge chromium rename ~/.config/chromium (which remained after purge, not sure if it should?) reboot $ sudo apt-get install chromium copy old Bookmarks to new ~/.config/chromium/Default/ Before this, I tried upgrading a VM with 16.04.1 to the latest version of chromium, which worked perfectly, and still worked after dist-upgrade to 16.04.2 - but the VM (and certainly its version of chromium) was pretty much otherwise unused, so I wondered aloud about potential causes. I don't see why a reboot should make a difference but I hope that works for you - mine is now working normally again. I should have explained more fully before. Gareth On Wed, 5 Jul 2017, at 14:05, Giuseppe_M wrote: > @Gareth Evans > > Your suggestion, and without copying back the old Bookmarks, works only > the first time, when you close and reopen the browser it crashes again, > with: > > Received signal 11 SEGV_MAPERR 0008 > #0 0xb762af0a base::debug::StackTrace::StackTrace() > #1 0xb762a83a base::debug::StackTrace::StackTrace() > #2 0xb762b388 > #3 0xb77bec20 ([vdso]+0xc1f) > #4 0x8055948a > #5 0x8055c01b > #6 0x8055c7d4 > #7 0x8055cb1b > #8 0x8086 > #9 0xb76afe2e > #10 0xb76afdb3 > #11 0xb762c80b base::debug::TaskAnnotator::RunTask() > #12 0xb7658f3b base::MessageLoop::RunTask() > #13 0xb765a292 base::MessageLoop::DeferOrRunPendingTask() > #14 0xb765b399 base::MessageLoop::DoWork() > #15 0xb765bfbd base::MessagePumpLibevent::Run() > #16 0xb7658304 base::MessageLoop::RunHandler() > #17 0xb76855dd base::RunLoop::Run() > #18 0xb76b5c61 base::Thread::ThreadMain() > #19 0xb76afcdf > #20 0xb7786295 start_thread > #21 0xafd6705e clone > gs: 0033 fs: es: 007b ds: 007b > edi: esi: a824bd60 ebp: 8f1507f8 esp: 8f150780 > ebx: 835cb528 edx: 8f150714 ecx: a824bcb0 eax: > trp: 000e err: 0004 ip: 8055948a cs: 0073 > efl: 00210282 usp: 8f150780 ss: 007b > [end of stack trace] > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1702407 > > Title: > Update breaks chromium-browser on Ubuntu Mate 16.04.2 > > Status in chromium-browser package in Ubuntu: > Confirmed > > Bug description: > $ apt-cache policy chromium-browser > chromium-browser: > Installed: 59.0.3071.109-0ubuntu0.16.04.1289 > Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 > Version table: >*** 59.0.3071.109-0ubuntu0.16.04.1289 500 > 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 > Packages > 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > 100 /var/lib/dpkg/status >49.0.2623.108-0ubuntu1.1233 500 > 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages > > $ chromium-browser > Using PPAPI flash. >--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so > --ppapi-flash-version= > Received signal 11 SEGV_MAPERR 0010 > #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() > #1 0x7f8cc1af580b > #2 0x7f8cc1e20390 > #3 0x5619ce286dc8 > #4 0x5619ce289656 > #5 0x5619ce289df9 > #6 0x5619ce28a143 > #7 0x7f8cc1b70821 > #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() > #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() > #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() > #11 0x7f8cc1b2283d > #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() > #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() > #14 0x7f8cc1b49628 base::RunLoop::Run() > #15 0x7f8cc1b75e36 base::Thread::ThreadMain() > #16 0x7f8cc1b70726 > #17 0x7f8cc1e166ba start_thread > #18 0x7f8cab4c53dd clone > r8: 002e r9: 5619cfcdd6ec r10: r11: > 7f8cab552f50 >r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: > 7f8c1b0d1eb0 > di: si: 7f8c1b0d1eb0 bp: 7f8c1b0d1f00 bx: > 7f8c1b0d1eb0 > dx: 0061 ax: cx: 7f8bf0047070 sp: > 7f8c1b0d1e60 > ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: > 0004 >trp: 000e msk: cr2: 0010 > [end of stack trace] > > Quits <1s after starting on desktop. Output from terminal-based launch is > above. > Worked earlier today before updating. > > To manage notifications about this bug go to: > https://bugs.l
[Bug 1702407] Re: Update breaks chromium-browser on Ubuntu Mate 16.04.2
$ ... chromium-browser, that is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Update breaks chromium-browser on Ubuntu Mate 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Update breaks chromium-browser on Ubuntu Mate 16.04.2
Thought I'd have a go out of interest - Replacing my new config dir with the old one reproduces the bug, but -dbg seems to require a previous verison of chromium-browser (had the the same problem trying to install -dbg from synaptic): === $ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse > deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted > universe multiverse > deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted > universe multiverse" | \ > sudo tee -a /etc/apt/sources.list.d/ddebs.list [sudo] password for user: deb http://ddebs.ubuntu.com xenial main restricted universe multiverse deb http://ddebs.ubuntu.com xenial-updates main restricted universe multiverse deb http://ddebs.ubuntu.com xenial-proposed main restricted universe multiverse $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 C8CAB6595FDFF622 Executing: /tmp/tmp.WR8LuQinDY/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 C8CAB6595FDFF622 gpg: requesting key 428D7C01 from hkp server keyserver.ubuntu.com gpg: requesting key 5FDFF622 from hkp server keyserver.ubuntu.com gpg: key 428D7C01: public key "Ubuntu Debug Symbol Archive Automatic Signing Key " imported gpg: key 5FDFF622: public key "Ubuntu Debug Symbol Archive Automatic Signing Key (2016) " imported gpg: Total number processed: 2 gpg: imported: 2 (RSA: 1) $ sudo apt-get update ... ... $ sudo apt-get install chromium-browser-dbg Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. chromium-browser-dbg : Depends: chromium-browser (= 51.0.2704.79-0ubuntu0.16.04.1.1242) but 59.0.3071.109-0ubuntu0.16.04.1289 is to be installed E: Unable to correct problems, you have held broken packages. In case it helps, the version I had installed previously (at least according to my update logs) was chromium-browser (58.0.3029.110-0ubuntu0.16.04.1281) Happy to help further if I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Update breaks chromium-browser on Ubuntu Mate 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Update breaks chromium-browser on Ubuntu Mate 16.04.2
Also I can switch config dirs to reproduce the bug and back again with no reboot necessary to result in normal operation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Update breaks chromium-browser on Ubuntu Mate 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831101] [NEW] rsync with remote sudo fails over ssh/pki with protocol mismatch error
Public bug reported: rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2 rsync version 3.1.2 protocol version 31 - same on local and remote OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 - same on local and remote I have checked for spurious output from .bashrc using $ ssh user@host /bin/true > out.dat which results in $ ls -l *.dat -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat -- The [redacted] command is rsync -AEavvvogt --rsync-path="sudo rsync" --debug=CONNECT -e "ssh -i /home/xxx/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --exclude-from=/home/xxx/backup.exclude --delete --link-dest=../$lastdt /etc $dest/$dt -- The [redacted] output is opening connection using: ssh -i /home/user/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l user xxx "sudo rsync" --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 (20 args) OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to xxx [192.168.1.120] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/user/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug1: Authenticating to xxx:22 as 'user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: MAC: compression: none debug1: kex: client->server cipher: MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: xxx Warning: Permanently added 'xxx,192.168.1.120' (ECDSA) to the list of known hosts. debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:xxx /home/user/.ssh/id_rsa debug1: Server accepts key: xxx debug1: Authentication succeeded (publickey). Authenticated to xxx ([192.168.1.120]:22). debug1: channel 0: new [client-session] debug1: Requesting debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype want_reply 0 debug1: tty_make_modes: no fd or tio debug1: Sending environment. debug1: Sending env LANG = en_GB.UTF-8 debug1: Sending command: sudo rsync --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) rsync error: protocol incompatibility (code 2) at compat.c(178) [sender=3.1.2] [sender] _exit_cleanup(code=2, file=compat.c, line=178): about to call exit(2) --- /etc/sudoers contains user ALL= NOPASSWD:/usr/bin/rsync ...which I have tried placing above (as is the default) and below lines beginning %admin and %sudo and the space in "ALL= NOPASSWD..." doesn't seem to make any difference I followed the instructions at https://www.digitalocean.com/community/tutorials/how-to-copy-files-with- rsync-over-ssh https://askubuntu.com/questions/719439/using-rsync-with-sudo-on-the- destination-machine ...which worked on 16.04, so I wonder if there may be a bug, although grateful for any other suggestions, as I am unsure how to debug/investigate further ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: rsync ** Tags added: rsync -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831101 Title: rsync with remote sudo fails over ssh/pki with protocol mismatch error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1831101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831101] Re: rsync with remote sudo fails over ssh/pki with protocol mismatch error
Not a bug. The problem seems to be -tt in the ssh options, which I had picked-up from somewhere as a possible solution, but https://bugzilla.redhat.com/show_bug.cgi?id=1019923 suggests rsync cannot be expected to work over ssh with -tt, albeit resulting there in a different error condition than I had encountered. Having corrected a remote path error, it seems to work as expected without -tt Thanks anyway for your help. ** Bug watch added: Red Hat Bugzilla #1019923 https://bugzilla.redhat.com/show_bug.cgi?id=1019923 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831101 Title: rsync with remote sudo fails over ssh/pki with protocol mismatch error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1831101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830121] Re: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch
I've discovered the problem was caused by -tt in the ssh options, which I picked up from somewhere as a step in debugging a prior issue. It works as expected once -tt is removed. Thanks anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830121 Title: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1830121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843662] [NEW] Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3)
Public bug reported: This bug affects the physical host machine, but seems to stem from virtualbox. After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. After reinstalling and update/dist-upgrade, dmesg contains the following: $ sudo dmesg | grep signature [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Ubuntu Mate 18.04 boot fails after upgrade from 4.15.0-20 to to 4.15.0-62 + Boot fails after upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3) ** Summary changed: - Boot fails after upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3) + Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3) ** Description changed: + This bug affects the physical host machine, but seems to stem from + virtualbox. + After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. After reinstalling and update/dist-upgrade, dmesg contains the following: $ sudo dmesg | grep signature - [sudo] password for user: + [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843662 Title: Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1843662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843662] Re: Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3)
** Description changed: This bug affects the physical host machine, but seems to stem from virtualbox. After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. After reinstalling and update/dist-upgrade, dmesg contains the following: $ sudo dmesg | grep signature [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key + + And (for future reference) is there a way to rescue an apparently + bricked machine? ** Description changed: This bug affects the physical host machine, but seems to stem from virtualbox. After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. - After reinstalling and update/dist-upgrade, dmesg contains the - following: + After reinstalling OS, and update/dist-upgrade, and reinstalling various + software (by custom script) dmesg contains the following: $ sudo dmesg | grep signature [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key And (for future reference) is there a way to rescue an apparently bricked machine? ** Description changed: This bug affects the physical host machine, but seems to stem from virtualbox. After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. - After reinstalling OS, and update/dist-upgrade, and reinstalling various - software (by custom script) dmesg contains the following: + After reinstalling OS, update/dist-upgrade, and reinstalling various + software, dmesg contains the following: $ sudo dmesg | grep signature [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key And (for future reference) is there a way to rescue an apparently bricked machine? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843662 Title: Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1843662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843662] Re: Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3)
** Description changed: This bug affects the physical host machine, but seems to stem from virtualbox. After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. After reinstalling OS, update/dist-upgrade, and reinstalling various software, dmesg contains the following: $ sudo dmesg | grep signature [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key + There are various references to occurrences of the error apparent at + boot time concerning NVIDIA drivers. I have onboard Intel graphics. + And (for future reference) is there a way to rescue an apparently bricked machine? ** Description changed: This bug affects the physical host machine, but seems to stem from virtualbox. After apt-get dist-upgrade upgraded kernel from 4.15.0-20 to to 4.15.0-62, the machine fails to boot after restart. The text: PKCS#7 signature not signed with a trusted key is repeated on 4 lines. Different shades of "black" as background to text appear at approx 1s intervals, then whole screen goes blank, this loops for at least 2 mins. No alternative terminals (Alt+Fx) are available. After reinstalling OS, update/dist-upgrade, and reinstalling various software, dmesg contains the following: $ sudo dmesg | grep signature [sudo] password for user: [ 1614.972768] PKCS#7 signature not signed with a trusted key [ 1614.973013] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 1615.015852] PKCS#7 signature not signed with a trusted key [ 1615.024261] PKCS#7 signature not signed with a trusted key [ 1615.032860] PKCS#7 signature not signed with a trusted key There are various references to occurrences of the error apparent at boot time concerning NVIDIA drivers. I have onboard Intel graphics. - And (for future reference) is there a way to rescue an apparently - bricked machine? + And (for future reference) is there a way to rescue a machine apparently + bricked in this way? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843662 Title: Boot fails after kernel upgrade from 4.15.0-20 to to 4.15.0-62 (Ubuntu Mate 18.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1843662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940631]
Still a problem on 60.4.0 (Ubuntu 18.04.1) There is one master password request per google-related thing - cardbook plugin for carddav, calendar - plus an extra one. Cancelling the first master password box results in the error: [Exception... "User canceled master password entry" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: jar:file:///usr/lib/thunderbird/omni.ja!/components/crypto-SDR.js :: decrypt :: line 177" data: no] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940631 Title: Thunderbird asks three times for my master password To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/940631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940631]
Correction to #52: Cardbook plugin is NOT used with a google account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940631 Title: Thunderbird asks three times for my master password To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/940631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810176] Re: libmtp error could not get object handles
I am experiencing this problem on Ubuntu Mate 18.04.2 reading/writing the /DCIM/Camera folder on a Samsung Galaxy S5 mini with Android 6.0.1 The first ~250 of 550 jpg images copy successfully, then file the operation window freezes and does not respond to clicking the cancel button. /var/log/syslog shows Jul 15 03:24:41 gvfsd[3824]: Error 2: Error 02ff: PTP I/O Error Jul 15 03:24:54 gvfsd[3824]: Error 2: PTP Layer error 02ff: LIBMTP_Get_Files_And_Folders(): could not get object handles. When /DCIM/Camera/ is accessed, Caja navigation freezes, eventually producing the "could not get object handles" error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810176 Title: libmtp error could not get object handles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1810176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699374] [NEW] connection refused due to pcap error?
Public bug reported: localhost:666 connection refused despite port 666 open. sudo darkstat -i --debug results in error message: 16527: error: pcap_open_live(): --debug: SIOCETHTOOL(ETHTOOL_GET_TS_INFO) ioctl failed: No such device Not sure if this is in any way related: https://github.com/Ettercap/ettercap/issues/408 Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: darkstat 3.0.719-1 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jun 21 03:42:57 2017 InstallationDate: Installed on 2017-01-13 (158 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: darkstat UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.darkstat.init.cfg: 2017-06-21T02:24:16.818519 ** Affects: darkstat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: connection refused due to pcap error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1699374] Re: connection refused due to pcap error?
eth0, wlan0 on Ubuntu are now named according to https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [1] user@tommy:~$ sudo darkstat -i wlp3s0 --debug error: illegal argument: "--debug" darkstat 3.0.719 (using libpcap version 1.7.4) user@tommy:~$ sudo darkstat -i wlp3s0 (and enp4s0) Appears to succeed, but http://... and https://localhost:666 and :1666 and http://:666 and :1666 all refuse connections from localhost, even with both ports specifically opened, or with firewall off. Same on Debian 9 with latest updates. Not sure if this is actually a darkstat bug - apologies if not but I can't see what's wrong otherwise. user@tommy:~$ ifconfig enp4s0Link encap:Ethernet HWaddr 20:6a:8a:97:52:82 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:17 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:3357 errors:0 dropped:0 overruns:0 frame:0 TX packets:3357 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:348724 (348.7 KB) TX bytes:348724 (348.7 KB) lxcbr0Link encap:Ethernet HWaddr 00:16:3e:00:00:00 inet addr:10.0.3.1 Bcast:0.0.0.0 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlp3s0Link encap:Ethernet HWaddr 1c:3e:84:56:ca:75 inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::c1e8:4ba3:b6e3:b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:413421 errors:0 dropped:0 overruns:0 frame:0 TX packets:247354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:583629884 (583.6 MB) TX bytes:30079108 (30.0 MB) -- Gareth Evans garethev...@fastmail.fm / text +44 (0)7967 641914 On Wed, 21 Jun 2017, at 04:19, Emil Mikulic wrote: > Try: sudo darkstat -i eth0 --debug > > The error message could be better, but it's saying there's no interface > called "--debug", which was the argument to -i. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1699374 > > Title: > connection refused due to pcap error? > > Status in darkstat package in Ubuntu: > New > > Bug description: > localhost:666 connection refused despite port 666 open. > > sudo darkstat -i --debug results in error message: > > 16527: error: pcap_open_live(): --debug: > SIOCETHTOOL(ETHTOOL_GET_TS_INFO) ioctl failed: No such device > > Not sure if this is in any way related: > https://github.com/Ettercap/ettercap/issues/408 > > Thanks > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: darkstat 3.0.719-1 > ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 > Uname: Linux 4.4.0-81-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > Architecture: amd64 > CurrentDesktop: MATE > Date: Wed Jun 21 03:42:57 2017 > InstallationDate: Installed on 2017-01-13 (158 days ago) > InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > SourcePackage: darkstat > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.darkstat.init.cfg: 2017-06-21T02:24:16.818519 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: connection refused due to pcap error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699374] Re: connection refused due to pcap error?
** Bug watch added: github.com/Ettercap/ettercap/issues #408 https://github.com/Ettercap/ettercap/issues/408 ** Description changed: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: connection refused due to pcap error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1699374] Re: connection refused due to pcap error?
Thank you, it's working on :667 https://unix4lyfe.org/darkstat/linuxformat.jpg says :666 though There are rather deep references in man darkstat to 667 but I hadn't looked because /etc/darkstat/init.cfg says PORT="-p 666" ...which seems to be ignored. Oh well, thanks again. Gareth On Wed, 21 Jun 2017, at 05:20, Emil Mikulic wrote: > The default webserver port should be 667. Try: "netstat -lntp" while > darkstat is running. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1699374 > > Title: > connection refused due to pcap error? > > Status in darkstat package in Ubuntu: > New > > Bug description: > localhost:666 connection refused despite port 666 open. > > sudo darkstat -i --debug results in error message: > > 16527: error: pcap_open_live(): --debug: > SIOCETHTOOL(ETHTOOL_GET_TS_INFO) ioctl failed: No such device > > Not sure if this is in any way related: > https://github.com/Ettercap/ettercap/issues/408 > > Thanks > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: darkstat 3.0.719-1 > ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 > Uname: Linux 4.4.0-81-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > Architecture: amd64 > CurrentDesktop: MATE > Date: Wed Jun 21 03:42:57 2017 > InstallationDate: Installed on 2017-01-13 (158 days ago) > InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > SourcePackage: darkstat > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.darkstat.init.cfg: 2017-06-21T02:24:16.818519 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: connection refused due to pcap error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699374] Re: connection refused due to pcap error?
On Ubuntu 16.04.2, it starts from :666 as specified in /etc/darkstat/init.cfg after a reboot. After this, changes to the config file port value seem to be observed following service darkstat restart. A little confusing but solved, thanks. ** Summary changed: - connection refused due to pcap error? + localhost:666 connection refused error? ** Description changed: - localhost:666 connection refused despite port 666 open. + After installation, localhost:666 connection refused despite port 666 + open. sudo darkstat -i --debug results in error message: 16527: error: pcap_open_live(): --debug: SIOCETHTOOL(ETHTOOL_GET_TS_INFO) ioctl failed: No such device Not sure if this is in any way related: https://github.com/Ettercap/ettercap/issues/408 Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: darkstat 3.0.719-1 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jun 21 03:42:57 2017 InstallationDate: Installed on 2017-01-13 (158 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: darkstat UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.darkstat.init.cfg: 2017-06-21T02:24:16.818519 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: localhost:666 connection refused error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699374] Re: localhost:666 connection refused error?
Not a bug as such as far is the software is concerned, but I wonder if confusion could be avoided if the port number value in the config file matched the actual default. As well as the Linux Format article (above), http://www.debianhelp.co.uk/darkstat.htm also gives wrong information. At least the right default in the config file would give a clue :) Just out of interest, has the default port ever been :666? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: localhost:666 connection refused error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699665] [NEW] Database config fails due to SQL error
Public bug reported: On installation config, mysql said: ERROR 1064 (42000) at line 2213: You have an error in your │ SQL syntax; check the manual that corresponds to your MariaDB server │ version for the right syntax to use near 'rows int(12) NOT NULL default │ '600', timespan int(12) unsigned NOT NULL defaul' at line 7 Ubuntu 16.04.2 apt-cache policy cacti cacti: Installed: 0.8.8f+ds1-4ubuntu4.16.04.2 Candidate: 0.8.8f+ds1-4ubuntu4.16.04.2 Version table: *** 0.8.8f+ds1-4ubuntu4.16.04.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe i386 Packages 100 /var/lib/dpkg/status 0.8.8f+ds1-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/universe i386 Packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cacti (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 05:56:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-13 (159 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: cacti Title: package cacti (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cacti (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699665 Title: Database config fails due to SQL error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/1699665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699374] Re: localhost:666 connection refused error?
Herewith the relevant part of comment #3, which has been hidden as I neglected to remove my email footer. *** eth0, wlan0 on Ubuntu are now named according to https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ user@tommy:~$ sudo darkstat -i wlp3s0 --debug error: illegal argument: "--debug" darkstat 3.0.719 (using libpcap version 1.7.4) user@tommy:~$ sudo darkstat -i wlp3s0 (and enp4s0) Appears to succeed, but http://... and https://localhost:666 and :1666 and http://:666 and :1666 all refuse connections from localhost, even with both ports specifically opened, or with firewall off. Same on Debian 9 with latest updates. Not sure if this is actually a darkstat bug - apologies if not but I can't see what's wrong otherwise. user@tommy:~$ ifconfig enp4s0 Link encap:Ethernet HWaddr 20:6a:8a:97:52:82 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:17 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:3357 errors:0 dropped:0 overruns:0 frame:0 TX packets:3357 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:348724 (348.7 KB) TX bytes:348724 (348.7 KB) lxcbr0 Link encap:Ethernet HWaddr 00:16:3e:00:00:00 inet addr:10.0.3.1 Bcast:0.0.0.0 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlp3s0 Link encap:Ethernet HWaddr 1c:3e:84:56:ca:75 inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::c1e8:4ba3:b6e3:b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:413421 errors:0 dropped:0 overruns:0 frame:0 TX packets:247354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:583629884 (583.6 MB) TX bytes:30079108 (30.0 MB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699374 Title: localhost:666 connection refused error? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1699374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1699665] Re: Database config fails due to SQL error
$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" $ mysql -V mysql Ver 15.1 Distrib 10.2.6-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Explanation and workaround: /usr/share/dbconfig-common/data/cacti/install/mysql includes: CREATE TABLE rra ( ... rows INT(12) NOT NULL DEFAULT '600', ... ) ENGINE=MYISAM; ROWS is a reserved word in MariaDB 10.2.4 upwards, according to https://mariadb.com/kb/en/mariadb/reserved-words/ If you change rows to `rows` (backticks required), the CREATE TABLE rra query succeeds, but the file /usr/share/dbconfig-common/data/cacti/install/mysql does not seem to exist until some time during the execution of dbconfig- common, so it seems its first attempt must fail. At this point I had to killall php every few mins to prevent memory, swap and CPU usage approaching 100% (since php restarts after a while). MariaDB [(none)]> drop database cacti; Query OK, 37 rows affected (0.03 sec) Edit the now-existing /usr/share/dbconfig-common/data/cacti/install/mysql to change ROWS to `rows` in CREATE TABLE rra Retry in dbconfig-common Installation succeeds. As an aside, SQLyog 12.4.2 x64 running under WINE 1.6.2 didn't actually drop the cacti database despite apparent success, as retrying in dbconfig-common then produced ERROR 1050 (42S01) at line 7: Table 'cdef' already exists so had to use terminal client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699665 Title: Database config fails due to SQL error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/1699665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1699665] Re: Database config fails due to SQL error
> Where did you get this from? This isn't a 16.04 Ubuntu package. https://downloads.mariadb.org/mariadb/repositories/#mirror=coreix&distro=Ubuntu&distro_release=xenial --ubuntu_xenial Thanks for the info - I'll bow to your judgement on whether it's worth fixing. Kind regards Gareth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699665 Title: Database config fails due to SQL error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/1699665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial
PPA updates fix the problem for me on 16.04.2 I'm curious as to why I couldn't install the debug symbols though - can anyone advise? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety
@Olivier, re #7,33,36 I see my mistake thanks to further posts and replies. I had spotted chromium-browser-dbg in synaptic and then had this package name in mind while misreading the more detailed instructions in the wiki link - it makes perfect sense on a calm reading! Anyway thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
