[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots

2019-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219

John  changed:

   What|Removed |Added

 CC||jlma...@gmail.com

--- Comment #1 from John  ---
One possible consideration for cause of this bug is via the 12 October 2019
14:58+000 UTC "pkg upgrade" is:

xorg-libraries-7.7_4 (direct dependency changed: libXScrnSaver)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"


maintainer-feedback requested: [Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots

2019-10-12 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-xfce mailing list
 for maintainer-feedback:
Bug 241219: x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes
User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219



--- Description ---
I have logged this issue against x11-wm/xfce4-wm as it is the only package that
was in the "pkg upgrade" 12 October 2019 14:58+000 UTC that I can guess as the
package causing the bug.  If this is an incorrect guess for ports package as
cause then for certain the bug "Summary" will need to be changed to reflect the
ports package causing the issue once confirmed as the source of the bug.

Since doing a FreeBSD "pkg upgrade" 12 October 2019 14:58+000 UTC both
x11/xfce4-screensaver and x11/xscreensaver fail in exact same manner resulting
in user having to force a system reboot or power cycle the system.

The last 'pkg upgrade" done was 02 October 2019 0326+000 UTC where both
x11/xfce4-screensaver and x11/xscreensaver behaved as expected.

The bug is identical for both x11/xfce4-screensaver and x11/xscreensaver.  The
bug is when either screensaver activates to black screen (current
configurations for both) neither mouse nor keyboard activity results in the
dialog box appearing asking for user password to unlock the screen.  Both have
been extensively tested and always fail exactly as described.
___
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"


[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots

2019-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219

Bug ID: 241219
   Summary: x11-wm/xfce4-wm: FreeBSD Update Causes XFCE
Screensavers Causes User Forced Reboots
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: Individual Port(s)
  Assignee: x...@freebsd.org
  Reporter: jlma...@gmail.com
  Assignee: x...@freebsd.org
 Flags: maintainer-feedback?(x...@freebsd.org)

Created attachment 208272
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208272=edit
Console when system was booted days prior to 12 October 2019 14:45+000 FreeBSD
Upgrade and the Upgrade Leading to Bug

I have logged this issue against x11-wm/xfce4-wm as it is the only package that
was in the "pkg upgrade" 12 October 2019 14:58+000 UTC that I can guess as the
package causing the bug.  If this is an incorrect guess for ports package as
cause then for certain the bug "Summary" will need to be changed to reflect the
ports package causing the issue once confirmed as the source of the bug.

Since doing a FreeBSD "pkg upgrade" 12 October 2019 14:58+000 UTC both
x11/xfce4-screensaver and x11/xscreensaver fail in exact same manner resulting
in user having to force a system reboot or power cycle the system.

The last 'pkg upgrade" done was 02 October 2019 0326+000 UTC where both
x11/xfce4-screensaver and x11/xscreensaver behaved as expected.

The bug is identical for both x11/xfce4-screensaver and x11/xscreensaver.  The
bug is when either screensaver activates to black screen (current
configurations for both) neither mouse nor keyboard activity results in the
dialog box appearing asking for user password to unlock the screen.  Both have
been extensively tested and always fail exactly as described.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"


[Bug 240110] x11-fm/thunar: use udisks2 to add support for removable storage devices

2019-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240110
Bug 240110 depends on bug 240138, which changed state.

Bug 240138 Summary: [NEW PORT] sysutils/libudisks: Library from udisks project, 
to access and manipulate disks, storage devices and technologies
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240138

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"


maintainer-feedback requested: [Bug 241212] x11-wm/xfce4: xfce-4.14 is broken! The error was 'GLXBadPixmap'!

2019-10-12 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-xfce mailing list
 for maintainer-feedback:
Bug 241212: x11-wm/xfce4: xfce-4.14 is broken! The error was 'GLXBadPixmap'!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241212



--- Description ---
After update Xfce to 4.14, I get errors:

Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 12 03:21:19 2019
(==) Using config file: "/etc/X11/xorg.conf"
gpg-agent[58995]: WARNING: "--write-env-file" is an obsolete option - it has no
effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:58974): xfce4-session-#[1;33mWARNING#[0m **:
#[34m03:21:23.428#[0m: gpg-agent returned no PID in the variables

(xfwm4:58996): Gdk-#[1;31mERROR#[0m **: #[34m03:21:26.414#[0m: The program
'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadPixmap'.
  (Details: serial 0 error_code 173 request_code 153 (GLX) minor_code 16)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

After that, I rollback to version 4.12 ...

root@vladiom:~ # pkg version -v | grep -e xorg -e pixman -e gdk -e glx -e gpg
gdk-pixbuf2-2.38.1 =   up-to-date with index
gpgme-1.13.1   =   up-to-date with index
gpgme-cpp-1.13.1   =   up-to-date with index
gpgme-qt5-1.13.1   =   up-to-date with index
gstreamer1-plugins-gdkpixbuf-1.14.4 =   up-to-date with index
libgpg-error-1.36  =   up-to-date with index
pixman-0.38.4  =   up-to-date with index
xorg-cf-files-1.0.6=   up-to-date with index
xorg-fonts-truetype-7.7_1  =   up-to-date with index
xorg-macros-1.19.2 =   up-to-date with index
xorg-server-1.18.4_12,1=   up-to-date with index
xorgproto-2019.1   =   up-to-date with index

root@vladiom:~ # pkg version -v | grep xfce
libxfce4menu-4.12.1_2  <   needs updating (index has 4.14.1)
libxfce4util-4.12.1<   needs updating (index has 4.14.0)
xfce-4.12_1<   needs updating (index has 4.14)
xfce-icons-elementary-0.13.1   =   up-to-date with index
xfce4-appfinder-4.12.0_1   <   needs updating (index has 4.14.0)
xfce4-bsdcpufreq-plugin-0.2_3  =   up-to-date with index
xfce4-conf-4.12.1  <   needs updating (index has 4.14.1)
xfce4-cpugraph-plugin-1.1.0_1  =   up-to-date with index
xfce4-desktop-4.12.5   <   needs updating (index has 4.14.1)
xfce4-mixer-4.11.0_5   =   up-to-date with index
xfce4-netload-plugin-1.3.2 =   up-to-date with index
xfce4-notes-plugin-1.8.1_2 =   up-to-date with index
xfce4-notifyd-0.4.4_1  =   up-to-date with index
xfce4-panel-4.12.2 <   needs updating (index has 4.14.1)
xfce4-screenshooter-plugin-1.9.5   <   needs updating (index has 1.9.6)
xfce4-session-4.12.1_6 <   needs updating (index has 4.14.0_1)
xfce4-settings-4.12.4_3<   needs updating (index has 4.14.1)
xfce4-systemload-plugin-1.2.3  =   up-to-date with index
xfce4-taskmanager-1.2.2_2  =   up-to-date with index
xfce4-terminal-0.8.8_1 =   up-to-date with index
xfce4-tumbler-0.2.7<   needs updating (index has 0.2.7_1)
xfce4-weather-plugin-0.10.0=   up-to-date with index
xfce4-whiskermenu-plugin-2.3.3 =   up-to-date with index
xfce4-wm-4.12.5_1  <   needs updating (index has 4.14.0_1)
xfce4-xkb-plugin-0.8.1_2   =   up-to-date with index

root@vladiom:~ # pkg version -v | grep nvidia
nvidia-driver-340-340.107_4=   up-to-date with index
nvidia-settings-435.21 =   up-to-date with index
nvidia-xconfig-435.21  =   up-to-date with index

root@vladiom:~ # uname -srm
FreeBSD 12.1-RC1 amd64

Whats wrong?
With Xfce 4.12 all works is fine!

P.S.
Second monitor is no detecting in Xfce 4.14 too!!!
___
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"


[Bug 241212] x11-wm/xfce4: xfce-4.14 is broken! The error was 'GLXBadPixmap'!

2019-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241212

Bug ID: 241212
   Summary: x11-wm/xfce4: xfce-4.14 is broken! The error was
'GLXBadPixmap'!
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: x...@freebsd.org
  Reporter: ad...@vladiom.com.ua
  Assignee: x...@freebsd.org
 Flags: maintainer-feedback?(x...@freebsd.org)

After update Xfce to 4.14, I get errors:

Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 12 03:21:19 2019
(==) Using config file: "/etc/X11/xorg.conf"
gpg-agent[58995]: WARNING: "--write-env-file" is an obsolete option - it has no
effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:58974): xfce4-session-#[1;33mWARNING#[0m **:
#[34m03:21:23.428#[0m: gpg-agent returned no PID in the variables

(xfwm4:58996): Gdk-#[1;31mERROR#[0m **: #[34m03:21:26.414#[0m: The program
'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadPixmap'.
  (Details: serial 0 error_code 173 request_code 153 (GLX) minor_code 16)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

After that, I rollback to version 4.12 ...

root@vladiom:~ # pkg version -v | grep -e xorg -e pixman -e gdk -e glx -e gpg
gdk-pixbuf2-2.38.1 =   up-to-date with index
gpgme-1.13.1   =   up-to-date with index
gpgme-cpp-1.13.1   =   up-to-date with index
gpgme-qt5-1.13.1   =   up-to-date with index
gstreamer1-plugins-gdkpixbuf-1.14.4 =   up-to-date with index
libgpg-error-1.36  =   up-to-date with index
pixman-0.38.4  =   up-to-date with index
xorg-cf-files-1.0.6=   up-to-date with index
xorg-fonts-truetype-7.7_1  =   up-to-date with index
xorg-macros-1.19.2 =   up-to-date with index
xorg-server-1.18.4_12,1=   up-to-date with index
xorgproto-2019.1   =   up-to-date with index

root@vladiom:~ # pkg version -v | grep xfce
libxfce4menu-4.12.1_2  <   needs updating (index has 4.14.1)
libxfce4util-4.12.1<   needs updating (index has 4.14.0)
xfce-4.12_1<   needs updating (index has 4.14)
xfce-icons-elementary-0.13.1   =   up-to-date with index
xfce4-appfinder-4.12.0_1   <   needs updating (index has 4.14.0)
xfce4-bsdcpufreq-plugin-0.2_3  =   up-to-date with index
xfce4-conf-4.12.1  <   needs updating (index has 4.14.1)
xfce4-cpugraph-plugin-1.1.0_1  =   up-to-date with index
xfce4-desktop-4.12.5   <   needs updating (index has 4.14.1)
xfce4-mixer-4.11.0_5   =   up-to-date with index
xfce4-netload-plugin-1.3.2 =   up-to-date with index
xfce4-notes-plugin-1.8.1_2 =   up-to-date with index
xfce4-notifyd-0.4.4_1  =   up-to-date with index
xfce4-panel-4.12.2 <   needs updating (index has 4.14.1)
xfce4-screenshooter-plugin-1.9.5   <   needs updating (index has 1.9.6)
xfce4-session-4.12.1_6 <   needs updating (index has 4.14.0_1)
xfce4-settings-4.12.4_3<   needs updating (index has 4.14.1)
xfce4-systemload-plugin-1.2.3  =   up-to-date with index
xfce4-taskmanager-1.2.2_2  =   up-to-date with index
xfce4-terminal-0.8.8_1 =   up-to-date with index
xfce4-tumbler-0.2.7<   needs updating (index has 0.2.7_1)
xfce4-weather-plugin-0.10.0=   up-to-date with index
xfce4-whiskermenu-plugin-2.3.3 =   up-to-date with index
xfce4-wm-4.12.5_1  <   needs updating (index has 4.14.0_1)
xfce4-xkb-plugin-0.8.1_2   =   up-to-date with index

root@vladiom:~ # pkg version -v | grep nvidia
nvidia-driver-340-340.107_4=   up-to-date with index
nvidia-settings-435.21 =   up-to-date with index
nvidia-xconfig-435.21  =   up-to-date with index

root@vladiom:~ # uname -srm
FreeBSD 12.1-RC1 amd64

Whats wrong?
With Xfce 4.12 all works is fine!

P.S.
Second monitor is no detecting in Xfce 4.14 too!!!

-- 
You are receiving this mail