FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ security/libzrtpcppcore | 4.6.3 | v4.6.4 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Qt5 applications broken: could not find or load the Qt platform plugin "xcb"
Hi, All Qt5 applications seem to be broken. When trying to start either of them, I get: [...] Fatal: This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: minimal, offscreen, xcb. Reinstalling the application may fix this problem. Abort (core dumped) [...] Reinstalling any of them didn't make a difference. Does anyone know what I'm missing here? Regards, Marco -- "Hey, Sam, how about a loan?" "Whattaya need?" "Oh, about $500." "Whattaya got for collateral?" "Whattaya need?" "How about an eye?" -- Sam Giancana ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Qt5 applications broken: could not find or load the Qt platform plugin "xcb"
Running pkg upgrade -f qt5-gui fixed this for me. On Fri, Nov 11, 2016, at 13:59, Marco Beishuizen wrote: > Hi, > > All Qt5 applications seem to be broken. When trying to start either of > them, I get: > > [...] > Fatal: This application failed to start because it could not find or load > the Qt platform plugin "xcb" > in "". > > Available platform plugins are: minimal, offscreen, xcb. > > Reinstalling the application may fix this problem. > > Abort (core dumped) > [...] > > Reinstalling any of them didn't make a difference. Does anyone know what > I'm missing here? > > Regards, > > Marco > > > -- > "Hey, Sam, how about a loan?" > "Whattaya need?" > "Oh, about $500." > "Whattaya got for collateral?" > "Whattaya need?" > "How about an eye?" > -- Sam Giancana > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Qt5 applications broken: could not find or load the Qt platform plugin "xcb"
rebuild qt5-gui 11.11.2016 19:59, Marco Beishuizen пишет: > Hi, > > All Qt5 applications seem to be broken. When trying to start either of > them, I get: > > [...] > Fatal: This application failed to start because it could not find or > load the Qt platform plugin "xcb" > in "". > > Available platform plugins are: minimal, offscreen, xcb. > > Reinstalling the application may fix this problem. > > Abort (core dumped) > [...] > > Reinstalling any of them didn't make a difference. Does anyone know what > I'm missing here? > > Regards, > > Marco > > -- - Alex. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Qt5 applications broken: could not find or load the Qt platform plugin "xcb"
On Fri, 11 Nov 2016, the wise Tobias Kortkamp wrote: Running pkg upgrade -f qt5-gui fixed this for me. Yes, this worked. Thanks for the pointer! Regards, Marco -- Divorce is a game played by lawyers. -- Cary Grant ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: databases/mariadb101-server / version 10.1.18 crashing
On 2016-11-10 3:34, Miroslav Lachman wrote: Miroslav Lachman wrote on 2016/11/09 15:43: Please update port to 10.1.19. It includes critical fixes https://jira.mariadb.org/browse/MDEV-10977 https://jira.mariadb.org/browse/MDEV-10394 We are getting following error on some machines too. ERROR] InnoDB: Block in space_id 0 in file /var/db/mysql/ibdata1 encrypted. Miroslav Lachman There is something terribly bad with MariaDB 10.1.18. I upgraded next machine which was previously working fine for years but keep crashing after upgrade. I strongly warn users before 10.1.18 version - if you have your databases created with some really old version and continously upgraded to 10.1, stay at 10.1.17 or expect unexpected crashes. This is one of many errors from logfile: InnoDB: Doing recovery: scanned up to log sequence number 36685500328 2016-11-10 3:13:59 34426872832 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 2016-11-10 3:14:00 34426872832 [Note] InnoDB: 128 rollback segment(s) are active. 2016-11-10 3:14:00 34426872832 [Note] InnoDB: Waiting for purge to start 2016-11-10 3:14:00 34426896384 [ERROR] InnoDB: Block in space_id 0 in file ./ibdata1 encrypted. 2016-11-10 3:14:00 34426896384 [ERROR] InnoDB: However key management plugin or used key_id 8 is not found or used encryption algorithm or method does not match. 2016-11-10 3:14:00 34426896384 [ERROR] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file. 2016-11-10 3:14:00 34426896384 [ERROR] InnoDB: Block in space_id 0 in file ./ibdata1 encrypted. 2016-11-10 3:14:00 34426896384 [ERROR] InnoDB: However key management plugin or used key_id 8 is not found or used encryption algorithm or method does not match. 2016-11-10 3:14:00 34426896384 [ERROR] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file. 161110 3:14:00 [ERROR] mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.18-MariaDB key_buffer_size=268435456 read_buffer_size=2097152 max_used_connections=0 max_threads=152 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5557219 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48400 0xb0238e at /usr/local/libexec/mysqld 0x723631 at /usr/local/libexec/mysqld 0x803211b4a at /lib/libthr.so.3 0x80321122c at /lib/libthr.so.3 The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 161110 03:14:00 mysqld_safe mysqld from pid file /var/db/mysql/elsa.pid ended It works fine after downgrade to 10.1.17 161110 03:28:41 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql 2016-11-10 3:28:41 34426872832 [Note] /usr/local/libexec/mysqld (mysqld 10.1.17-MariaDB) starting as process 75826 ... 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-11-10 3:28:41 34426872832 [Note] InnoDB: The InnoDB memory heap is disabled 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-11-10 3:28:41 34426872832 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Using generic crc32 instructions 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Initializing buffer pool, size = 256.0M 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Completed initialization of buffer pool 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Highest supported file format is Barracuda. 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Log scan progressed past the checkpoint lsn 36685481501 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Database was not shutdown normally! 2016-11-10 3:28:41 34426872832 [Note] InnoDB: Starting crash recovery. 2016-11-10 3:28
Re: Qt5 applications broken: could not find or load the Qt platform plugin "xcb"
Em Fri, 11 Nov 2016 15:07:34 +0100 (CET), Marco Beishuizen escreveu > On Fri, 11 Nov 2016, the wise Tobias Kortkamp wrote: > > > Running pkg upgrade -f qt5-gui fixed this for me. > > > > Yes, this worked. Thanks for the pointer! > > Regards, > Marco Hi Marcos, when I update my sustem on november 3, I need to force the pkg to reeinstall all qt 5.6 packeges, because it's not upgrade all correct > > -- > Divorce is a game played by lawyers. > -- Cary Grant > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" --- /* **Nilton José RizzoUFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
