[Bug 1888130] Re: Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - fixed in Jogl 2.4.0
** Summary changed: - Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0 + Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - fixed in Jogl 2.4.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888130 Title: Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - fixed in Jogl 2.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjogl2-java/+bug/1888130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888130] [NEW] Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0
Public bug reported: My JOGL applications stopped working on Ubuntu 20.04 - with the following error/exception: "Profile GL4bc is not available on X11GraphicsDevice". (I am using the Intel GPU of a Core i5-7600) In the jogamp forum, someone posted the same problem: http://forum.jogamp.org/Crash-after-latest-mesa-driver-update-from-ppa- oibaf-td4040300.html The suggested to solution to use the Jogl 2.4.0 release candidate also works on my system. (I would suggest to switch to 2.4.0 RC, as 2.3.2 does not work at all here; of course, we could also try to identify the required patch) ** Affects: libjogl2-java (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/1888130 Title: Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjogl2-java/+bug/1888130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888130] Re: Jogl 2.3.2 crashes wtih "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0
Notably, JOGL initially worked on my Ubuntu 20.04 installation. Some update seems to have broken it (I only have official Ubuntu package repositories enabled, no PPAs whatsoever) ** Summary changed: - Jogl 2.3.2 crashes wtih "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0 + Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888130 Title: Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice" - solved in Jogl 2.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjogl2-java/+bug/1888130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
With the Ubuntu Mate desktop, the window displacement issue does not occur on my system. I just tried this - using different compositors (Marco and Compiz). So until the window displacement issue is resolved, I am tempted to stick to Ubuntu Mate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
Looking at the /var/log/Xorg.0.log, it appears that the Iiyama screen is
considered disconnected on standby - and the reconnect causes a relayout
of the desktop.
I wonder if it's possible to simply suppress or ignore those hotplug
events (?)
This is the output in the /var/log/Xorg.0.log on a standby cycle:
[ 31292.359] (--) NVIDIA(GPU-0): DFP-6: disconnected
[ 31292.359] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[ 31292.359] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[ 31292.359] (--) NVIDIA(GPU-0):
[ 31292.362] (--) NVIDIA(GPU-0): CRT-0: disconnected
[ 31292.362] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 31292.362] (--) NVIDIA(GPU-0):
[ 31292.365] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 31292.365] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0):
[ 31292.365] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 31292.365] (--) NVIDIA(GPU-0): DFP-1: 330.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0):
[ 31292.365] (--) NVIDIA(GPU-0): DFP-2: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[ 31292.365] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0):
[ 31292.365] (--) NVIDIA(GPU-0): DFP-3: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 31292.365] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0):
[ 31292.366] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): connected
[ 31292.366] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): Internal DisplayPort
[ 31292.366] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): 960.0 MHz maximum pixel
clock
[ 31292.366] (--) NVIDIA(GPU-0):
[ 31292.366] (--) NVIDIA(GPU-0): DFP-5: disconnected
[ 31292.366] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[ 31292.366] (--) NVIDIA(GPU-0): DFP-5: 330.0 MHz maximum pixel clock
[ 31292.366] (--) NVIDIA(GPU-0):
[ 31292.366] (--) NVIDIA(GPU-0): DFP-6: disconnected
[ 31292.366] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[ 31292.366] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[ 31292.366] (--) NVIDIA(GPU-0):
[ 31292.366] (--) NVIDIA(GPU-0): DFP-7: disconnected
[ 31292.366] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[ 31292.366] (--) NVIDIA(GPU-0): DFP-7: 330.0 MHz maximum pixel clock
[ 31292.366] (--) NVIDIA(GPU-0):
[ 31292.573] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @3840x2160
+0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}"
[ 31292.987] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID
for display
[ 31292.987] (**) NVIDIA(0): device Idek Iiyama PL2888UH (DFP-6) (Using EDID
[ 31292.987] (**) NVIDIA(0): frequencies has been enabled on all display
devices.)
[ 31292.992] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): connected
[ 31292.992] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): Internal
DisplayPort
[ 31292.992] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): 960.0 MHz
maximum pixel clock
[ 31292.992] (--) NVIDIA(GPU-0):
[ 31293.113] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @3840x2160
+0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, DP-4:
nvidia-auto-select @3840x2160 +3840+0 {ViewPortIn=3840x2160,
ViewPortOut=3840x2160+0+0}"
[ 31293.482] (--) NVIDIA(GPU-0): CRT-0: disconnected
[ 31293.482] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 31293.483] (--) NVIDIA(GPU-0):
[ 31293.485] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 31293.485] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 31293.485] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 31293.485] (--) NVIDIA(GPU-0):
[ 31293.488] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 31293.489] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 31293.489] (--) NVIDIA(GPU-0): DFP-1: 330.0 MHz maximum pixel clock
[ 31293.489] (--) NVIDIA(GPU-0):
[ 31293.489] (--) NVIDIA(GPU-0): DFP-2: disconnected
[ 31293.489] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[ 31293.489] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[ 31293.489] (--) NVIDIA(GPU-0):
[ 31293.489] (--) NVIDIA(GPU-0): DFP-3: disconnected
[ 31293.489] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 31293.489] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 31293.489] (--) NVIDIA(GPU-0):
[ 31293.489] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): connected
[ 31293.489] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): Internal DisplayPort
[ 31293.489] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): 960.0 MHz maximum pixel
clock
[ 31293.489] (--) NVIDIA(GPU-0):
[ 31293.490] (--) NVIDIA(GPU-0): DFP-5: disconnected
[ 31293.490] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[ 31293.490] (--) NVIDIA(GPU-0): DFP-5: 330.0 MHz maximum pixel clock
[ 31293.490] (--) NVIDIA(GPU-0):
[ 31293.490] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): connected
[ 31293.490] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): Internal
DisplayPort
[ 31293.490]
[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
I have this problem in Ubuntu 14.04 and 16.04 with a dual 4K screen
setup (using a nvidia GPU).
Sometimes when waking the screens from standby ("Power Save Mode"), windows on
the right screen are moved to an invisible offscreen area.
Using keyboard shortcuts, they can be moved to the visible area again.
I just ran my screens through ~10 standby cycles in different configurations.
One screen (Dell) wakes from standby almost immediately - the other (Iiyama)
needs around 3 seconds. For simplicity, I will refer to them as quick and slow
screen.
Both screens are connected via DisplayPort.
The driver from Ubuntu's nvidia-361 package is used.
I made the following observations:
* Window displacement happens on the right screen only.
* When the quick screen is the right screen, you can see the windows at the
correct positions after wakeup, then the slow screen wakes up, reinitialization
seems to be triggered (both screens are black for one second) and after that
the windows are displaced (sometimes).
* When the quick screen is the right screen, random displacement seems to
happen only once per Unity Session (if I logged out and in again, it happened
again). When the slow screen is the right screen, it happens more often.
* When window displacement occurs, windows seem to be swapped between the right
screen and the invisible offscreen area (-> windows still in the invisible
offscreen area reappear at their former positions).
* Swapping the DisplayPort connectors at the Graphics Adapter does not have an
impact on the behaviour.
* KDE also displaces windows on wakeup. They are moved to screen edges instead
of invisible offscreen areas.
---
I am using the tint2 taskbar (window displacement also occurs without tint2).
Its command line output at screen wakeup might be interesting.
There are two variants of output (see below). Window displacement may occur on
either.
If displacement occurs, tint2 and also the menus in the title bar are often
broken on one screen - until I restart tint2.
First variant:
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1163: triggering tint2 restart due
to configuration change in the root window
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1883: restarting tint2...
xRandr: Found crtc's: 3
xRandr: Linking output DP-2 with crtc 0
xRandr: Linking output DP-4 with crtc 1
xsettings: Gtk/FontName = Ubuntu 11
xsettings: Net/IconThemeName = ubuntu-mono-dark
real transparency on... depth: 32
panel items: TSC
Systray composited rendering on
tint2 : nb monitor 2, nb monitor used 2, nb desktop 1
Kernel uevent interface initialized...
Second variant:
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1163: triggering tint2 restart due
to configuration change in the root window
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1883: restarting tint2...
xRandr: Found crtc's: 3
xRandr: Linking output DP-2 with crtc 0
xsettings: Gtk/FontName = Ubuntu 11
xsettings: Net/IconThemeName = ubuntu-mono-dark
real transparency on... depth: 32
panel items: TSC
Systray composited rendering on
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Kernel uevent interface initialized...
tint2 : another systray is running pid=1908
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1163: triggering tint2 restart due
to configuration change in the root window
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1883: restarting tint2...
xRandr: Found crtc's: 3
xRandr: Linking output DP-2 with crtc 0
xRandr: Linking output DP-4 with crtc 1
xsettings: Gtk/FontName = Ubuntu 11
xsettings: Net/IconThemeName = ubuntu-mono-dark
real transparency on... depth: 32
panel items: TSC
Systray composited rendering on
tint2 : nb monitor 2, nb monitor used 2, nb desktop 2
Kernel uevent interface initialized...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295267
Title:
Windows change Monitor/Desktop after screen lock
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215572] Re: [saucy] c++config.h missing in i386
I believe this bug is fixed in Ubuntu 14.04. I have the same kind of clang compiler errors with Ubuntu 13.10 (i386). They no longer occur with Ubuntu 14.04 (i386; using clang-3.4). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215572 Title: [saucy] c++config.h missing in i386 To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1215572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 743208] [NEW] wishlist: bash completion for colormake
Public bug reported: Binary package hint: bash-completion Bash completion is enabled for GNU make and several variants such as pmake. However, there is no tab completion for colormake (yet) (also checked Natty Narwhal package). I often use it and guess it could be added with little effort (?) - which would be great. Thanks. ** Affects: bash-completion (Ubuntu) Importance: Undecided Status: New ** Tags: bash-completion colormake -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743208 Title: wishlist: bash completion for colormake -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 743208] Re: wishlist: bash completion for colormake
** Patch added: I guess this is how it's done https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/743208/+attachment/1943451/+files/make.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743208 Title: wishlist: bash completion for colormake -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464199] Re: intel pro/wireless 5100 AGN disabled
OK... I found this in my syslog: Oct 31 19:45:08 protoomega NetworkManager: info Found radio killswitch rfkill2 (at /sys/devices/pci:00/:00:1c.1/:0c:00.0/ieee80211/phy0/rfkill2) (driver unknown) Oct 31 19:45:08 protoomega NetworkManager: info Found radio killswitch rfkill0 (at /sys/devices/virtual/rfkill/rfkill0) (driver unknown) Oct 31 19:45:08 protoomega NetworkManager: info Wireless now disabled by radio killswitch As these messages indicate, the notebook has a slightly hidden switch (at the side) to enable and disable WLAN - and it works perfectly with Ubuntu... (this is so very, very embarassing indeed ... ) So no problem here. Hopefully, some of the posted links will help nevertheless. -- intel pro/wireless 5100 AGN disabled https://bugs.launchpad.net/bugs/464199 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
