Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
On Fri, Jul 29, 2016 at 12:26:49AM -0500, Justin Haynes wrote: > List - > > I am having a problem starting Gnome 3 on my Thinkpad x61s, and I am not > sure what the cause is. I am reading mixed reviews on whether or not it is > necessary to have 3d support, and as nearly as i can tell i do have 3d > support on this Intel 965 x3100 display through the intel driver and the > i965 DRI driver in X-Windows. > > The problem is that when i attempt ot start Gnome using gdm, I get nothing > but X Windows with a black background and the X mouse cursor. > > Any other method I use yields either the entire root window in grey with > the text: > > "Oh no! something has gone wrong." > "A problem has occurred and the system can't recover. All extensions have > been disabled as a precaution." > > In summary I have tried the following: > > 1. GDM How did you install gnome? And did you do the steps in /usr/local/share/doc/pkg-readmes/gnome-* ? How do you start GDM ? Also a complete dmesg and the content of /var/log/gdm/* could be of interest. > 2. startx, with .xinitrc containing "exec /usr/local/bin/ck-launch-session > /usr/local/bin/gnome-session" > 3. From Window Maker: "/usr/local/bin/ck-launch-session > /usr/local/bin/gnome-session" > 4. reboot, and with boot -c, "disable inteldrm". Thinking that perhaps i > needed X to talk with the hardware without the kernel driver. > (machdep.allowaperture is already = 2) (with gdm) > 5. same as #4 without gdm > 6. same as 4, but with windowmaker like in 3. > > > I do have this appearing in my XOrg.log: > . > [ 1530.853] (II) intel(0): [XvMC] i965_xvmc driver initialized. > [ 1530.853] (II) intel(0): [DRI2] Setup complete > [ 1530.853] (II) intel(0): [DRI2] DRI driver: i965 > [ 1530.853] (II) intel(0): [DRI2] VDPAU driver: i965 > [ 1530.853] (II) intel(0): direct rendering: DRI2 enabled > . > > $ glxinfo | grep -i 3D > GL_3DFX_texture_compression_FXT1, GL_AMD_seamless_cubemap_per_texture, > GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, > GL_OES_surfaceless_context, GL_OES_texture_3D, GL_OES_texture_float, > > > I'll now send this message and gather more of the logs to make available, > starting with #1; GDM. -- Antoine
Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
List - I am having a problem starting Gnome 3 on my Thinkpad x61s, and I am not sure what the cause is. I am reading mixed reviews on whether or not it is necessary to have 3d support, and as nearly as i can tell i do have 3d support on this Intel 965 x3100 display through the intel driver and the i965 DRI driver in X-Windows. The problem is that when i attempt ot start Gnome using gdm, I get nothing but X Windows with a black background and the X mouse cursor. Any other method I use yields either the entire root window in grey with the text: "Oh no! something has gone wrong." "A problem has occurred and the system can't recover. All extensions have been disabled as a precaution." In summary I have tried the following: 1. GDM 2. startx, with .xinitrc containing "exec /usr/local/bin/ck-launch-session /usr/local/bin/gnome-session" 3. From Window Maker: "/usr/local/bin/ck-launch-session /usr/local/bin/gnome-session" 4. reboot, and with boot -c, "disable inteldrm". Thinking that perhaps i needed X to talk with the hardware without the kernel driver. (machdep.allowaperture is already = 2) (with gdm) 5. same as #4 without gdm 6. same as 4, but with windowmaker like in 3. I do have this appearing in my XOrg.log: . [ 1530.853] (II) intel(0): [XvMC] i965_xvmc driver initialized. [ 1530.853] (II) intel(0): [DRI2] Setup complete [ 1530.853] (II) intel(0): [DRI2] DRI driver: i965 [ 1530.853] (II) intel(0): [DRI2] VDPAU driver: i965 [ 1530.853] (II) intel(0): direct rendering: DRI2 enabled . $ glxinfo | grep -i 3D GL_3DFX_texture_compression_FXT1, GL_AMD_seamless_cubemap_per_texture, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_OES_surfaceless_context, GL_OES_texture_3D, GL_OES_texture_float, I'll now send this message and gather more of the logs to make available, starting with #1; GDM.
[UPDATE] sysutils/fabric-1.11.1 -> 1.12.0
Hi ports@, Attached you can find an update to the sysutils/fabric port. Kind regards. -- Pablo Méndez Hernández Index: Makefile === RCS file: /cvs/ports/sysutils/fabric/Makefile,v retrieving revision 1.2 diff -u -p -r1.2 Makefile --- Makefile11 Apr 2016 19:16:45 - 1.2 +++ Makefile29 Jul 2016 05:14:54 - @@ -2,7 +2,7 @@ COMMENT = simple, pythonic tool for remote execution and deployment -MODPY_EGG_VERSION =1.11.1 +MODPY_EGG_VERSION =1.12.0 DISTNAME = Fabric-${MODPY_EGG_VERSION} PKGNAME = ${DISTNAME:L} Index: distinfo === RCS file: /cvs/ports/sysutils/fabric/distinfo,v retrieving revision 1.2 diff -u -p -r1.2 distinfo --- distinfo11 Apr 2016 19:16:45 - 1.2 +++ distinfo29 Jul 2016 05:14:54 - @@ -1,2 +1,2 @@ -SHA256 (Fabric-1.11.1.tar.gz) = M2z6M1hAE2+rhpSlOd1hkkaXuNDC86Eq+t8KYWXAh10= -SIZE (Fabric-1.11.1.tar.gz) = 215069 +SHA256 (Fabric-1.12.0.tar.gz) = +voX1poV/Wrl+C0orL+Q4b8V49dDj78OhpGGgWTA6dw= +SIZE (Fabric-1.12.0.tar.gz) = 232840 Index: pkg/PLIST === RCS file: /cvs/ports/sysutils/fabric/pkg/PLIST,v retrieving revision 1.2 diff -u -p -r1.2 PLIST --- pkg/PLIST 11 Apr 2016 19:16:45 - 1.2 +++ pkg/PLIST 29 Jul 2016 05:14:54 - @@ -1,12 +1,11 @@ -@comment $OpenBSD: PLIST,v 1.2 2016/04/11 19:16:45 juanfra Exp $ -@conflict py-fabric-* -@pkgpath sysutils/py-fabric +@comment $OpenBSD$ bin/fab lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/ lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/SOURCES.txt lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/dependency_links.txt lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/entry_points.txt +lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/pbr.json lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/requires.txt lib/python${MODPY_VERSION}/site-packages/Fabric-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/top_level.txt lib/python${MODPY_VERSION}/site-packages/fabric/
Re: windowmaker diff
No objections, and another confirmation here! Thought I am running OpenBSD 5.9 RELEASE with the ports distributed with that release, the diff still worked well. I only had 36 lines of Makefile.rej to process from the patch and I am for the first time since I wanted to in the late 90s using *drawers* on the dock. :-) I'm so happy. Also, I notice that Chrome docks properly. This was a problem in .92. I tested out the Workspace pager, and it works just fine. The additional maximize options (to left, right top and bottom halves, and to the corners) are all working. Thanks for your work reyk, sebastia and David!
Re: Security update textproc/wkhtmltopdf-0.12.3.2
On Thu, Jul 28, 2016 at 12:54:52PM +0100, Stuart Henderson wrote: > On 2016/07/28 01:02, Tinker wrote: > > On 2016-07-27 16:36, Frank Groeneveld wrote: > > > Attached patch updates wkhtmltopdf to the latest release. Some important > > > security fixes (OpenSSL updates) were added .. > > > > Can't it use the system's LibreSSL version?? > > > > I'm pretty sure it is, otherwise we wouldn't have needed the OPENSSL_NO_SSL3 > patches. Yes, it doesn't use the bundled OpenSSl version, sorry for the confusion. It seems the 0.12.3.1 and 0.12.3.2 releases are mostly done for Windows users which do use the bundled OpenSSL: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.3.2 https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.3.1 Other platforms only need the fixes that were done in 0.12.3, which according to the changelog, don't include security fixes: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.3 I'll bring this patch up again after the lock is removed, because without security issues there is no rush this port update. Frank
Re: nginx / dav
On Wed, Jul 27, 2016 at 2:19 PM, Antoine Jacoutotwrote: > On Wed, Jul 27, 2016 at 12:32:28PM -0400, sven falempin wrote: > > It s compiling well. > > I wonder if it could not be on by default... > it works * i also make it run for a night with GET and PUT in loops , MKCOL and DELETE are ok too I wonder why they did not code PROPFIND > > ===> Building package for nginx-1.9.10-lua-dav > > Create /usr/ports/packages/amd64/all/nginx-1.9.10-lua-dav.tgz > > Link to /usr/ports/packages/amd64/ftp/nginx-1.9.10-lua-dav.tgz > > Link to /usr/ports/packages/amd64/cdrom/nginx-1.9.10-lua-dav.tgz > > > > Index: Makefile > > === > > RCS file: /cvs/ports/www/nginx/Makefile,v > > retrieving revision 1.89 > > diff -u -p -r1.89 Makefile > > --- Makefile26 Jan 2016 20:42:56 - 1.89 > > +++ Makefile27 Jul 2016 16:15:29 - > > @@ -29,7 +29,7 @@ NGINX_DIR=/var/www > > SUBST_VARS=NGINX_DIR > > CFLAGS+= -Wall -Wpointer-arith > > > > -FLAVORS= lua naxsi passenger > > +FLAVORS= lua naxsi passenger dav > > FLAVOR?= > > > > .if !${FLAVOR:Mpassenger} > > @@ -73,6 +73,10 @@ CONFIGURE_ARGS+= --prefix=${NGINX_DIR} \ > > --without-mail_pop3_module \ > > --without-mail_imap_module \ > > --without-mail_smtp_module > > + > > +.if ${FLAVOR:Mdav} > > +CONFIGURE_ARGS+= --with-http_dav_module > > +.endif > > > > DISTFILES+=${DISTNAME}${EXTRACT_SUFX} > > PATCHFILES+= nginx_chroot-20151002.patch:2 > > cvs server: Diffing patches > > cvs server: Diffing pkg > > > > In case someone wants it. > > > > -- > > > - > > () ascii ribbon campaign - against html e-mail > > /\ > > -- > Antoine > -- - () ascii ribbon campaign - against html e-mail /\
Re: Security update textproc/wkhtmltopdf-0.12.3.2
On 2016/07/28 01:02, Tinker wrote: > On 2016-07-27 16:36, Frank Groeneveld wrote: > > Attached patch updates wkhtmltopdf to the latest release. Some important > > security fixes (OpenSSL updates) were added .. > > Can't it use the system's LibreSSL version?? > I'm pretty sure it is, otherwise we wouldn't have needed the OPENSSL_NO_SSL3 patches.