[Bug 1770742] Re: Cannot find -lGL

2018-07-28 Thread DeathByDenim via ubuntu-bugs
Oh, sorry. I'm really late to reply to this. Yeah, I do have the
proprietary nVidia drivers installed. Those drivers came from the
default Ubuntu repositories.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770742

Title:
  Cannot find -lGL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770742] [NEW] Cannot find -lGL

2018-05-11 Thread DeathByDenim via ubuntu-bugs
Public bug reported:

I was trying to compile a OpenGL program, but it fails to compile. I
suppose the package this bug is in is really libglvnd-dev, but I could
not find that in Launchpad.

Anyway, the linking error is:
/usr/bin/x86_64-linux-gnu-ld: cannot find -lGL
collect2: error: ld returned 1 exit status

This seems to be because the symlink libGL.so is missing. If I go to 
/usr/lib/x86_64-linux-gnu and type:
  sudo ln -s libGL.so.1 libGL.so
then compiling works.

Here is a (nonsensical) test program:
#include 

int main(int argc, char *argv[])
{
glEnable(GL_DEPTH_TEST);

return 0;
}

which I compile with:
  gcc testgl.c -lGL

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1 1.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 11 15:48:17 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-29 (12 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libglvnd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770742

Title:
  Cannot find -lGL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769461] [NEW] Crash on heaptrack analysis

2018-05-06 Thread DeathByDenim via ubuntu-bugs
Public bug reported:

KDevelop crashes when selecting Run -> Run Heaptrack Analysis even
though heaptrack and heaptrack-gui are installed.

To reproduce:
1. Create new Terminal project with default template.
2. Compile code and observe that it works.
3. From the menu select Run -> Run Heaptrack Analysis
4. KDevelop crashes due to segmentation fault

Output from running kdevelop from the terminal:
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdevelop path = /usr/bin pid = 11158
KCrash: Arguments: /usr/bin/kdevelop 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 24 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
[1]+  Segmentatiefout (geheugendump gemaakt) kdevelop

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kdevelop 4:5.2.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Sun May  6 10:09:24 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-29 (6 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: kdevelop
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kdevelop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769461

Title:
  Crash on heaptrack analysis

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1769461/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1755812] [NEW] Next button not visible during install in VirtualBox

2018-03-14 Thread DeathByDenim via ubuntu-bugs
Public bug reported:

I downloaded the Kubuntu 18.04-beta1 iso and did an install in
VirtualBox 5.0.40_Ubuntu r115130. During the install the screen was too
small to show the Next button. Resizing the virtualbox window had no
effect.

Workaround is to use the Tab button and guess when the Next button is
selected.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Mar 14 09:26:20 2018
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2018-03-14 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
JournalErrors:
 -- Logs begin at Wed 2018-03-14 09:17:25 EDT, end at Wed 2018-03-14 09:24:41 
EDT. --
 Mar 14 09:17:25 hostname kernel: piix4_smbus :00:07.0: SMBus base address 
uninitialized - upgrade BIOS or use force_addr=0xaddr
 Mar 14 09:19:18 hostname spice-vdagent[1149]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
 Mar 14 09:19:36 hostname pulseaudio[1074]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive 
a reply. Possible causes include: the remote application did not send a reply, 
the message bus security policy blocked the reply, the reply timeout expired, 
or the network connection was broken.
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755812

Title:
  Next button not visible during install in VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755812/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs