[Desktop-packages] [Bug 1709399] Re: LLVM symbols should be versioned to avoid crashing applications that load mesa's swrast and also use a different libLLVM

2018-07-07 Thread RJVB
It seems that this could have been backported by now, the ticket has
been open for (almost) a year now ...

In the end I got fed up with having to point the library used by
Mesa/Gallium to the much newer one I also use (something kept resetting
it), and uninstalled the corresponding Mesa component. Problem not
solved but gone all the same (and I don't notice any difference other
than that certain applications no longer crash).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1709399

Title:
  LLVM symbols should be versioned to avoid crashing applications that
  load mesa's swrast and also use a different libLLVM

Status in llvm-toolchain-3.8 package in Ubuntu:
  Confirmed

Bug description:
  The libgl1-mesa-dri-lts-xenial package depend on libLLVM-3.8.so.1 from
  the libllvm3.8v4 package; this library gets used when using software
  OpenGL rendering on a remote display. As a result, applications based
  on Qt5 that also use libLLVM features provided by another (newer) LLVM
  version will crash when invoked from a remote X terminal.

  Example: KDevelop5 uses libclang (and this libLLVM) for C/C++ parsing;
  I build it to use the LLVM/Clang 4.0 packages from llvm.org (and self-
  built Qt5 and KF5 libraries) and can thus not render to a remote X
  server (XQuartz on my Mac).

  There is an upstream LLVM patch which solves the issue by adding
  versioning info to libLLVM:

  https://bugs.kde.org/show_bug.cgi?id=373614
  https://reviews.llvm.org/D31524

  Please consider backporting this patch to LLVM 3.8 (or rebuilding the
  mesa package to use a (much) more recent LLVM version that already
  contains the patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1709399/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1709399] [NEW] LLVM symbols should be versioned to avoid crashing applications that load mesa's swrast and also use a different libLLVM

2017-08-08 Thread RJVB
Public bug reported:

The libgl1-mesa-dri-lts-xenial package depend on libLLVM-3.8.so.1 from
the libllvm3.8v4 package; this library gets used when using software
OpenGL rendering on a remote display. As a result, applications based on
Qt5 that also use libLLVM features provided by another (newer) LLVM
version will crash when invoked from a remote X terminal.

Example: KDevelop5 uses libclang (and this libLLVM) for C/C++ parsing; I
build it to use the LLVM/Clang 4.0 packages from llvm.org (and self-
built Qt5 and KF5 libraries) and can thus not render to a remote X
server (XQuartz on my Mac).

There is an upstream LLVM patch which solves the issue by adding
versioning info to libLLVM:

https://bugs.kde.org/show_bug.cgi?id=373614
https://reviews.llvm.org/D31524

Please consider backporting this patch to LLVM 3.8 (or rebuilding the
mesa package to use a (much) more recent LLVM version that already
contains the patch).

** Affects: llvm-toolchain-3.8 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  The libgl1-mesa-dri-lts-xenial package depend on libLLVM-3.8.so.1 from
  the libllvm3.8v4 package; this library gets used when using software
  OpenGL rendering on a remote display. As a result, applications based on
  Qt5 that also use libLLVM features provided by another (newer) LLVM
  version will crash when invoked from a remote X terminal.
  
  Example: KDevelop5 uses libclang (and this libLLVM) for C/C++ parsing; I
  build it to use the LLVM/Clang 4.0 packages from llvm.org (and self-
  built Qt5 and KF5 libraries) and can thus not render to a remote X
  server (XQuartz on my Mac).
  
  There is an upstream LLVM patch which solves the issue by adding
  versioning info to libLLVM:
  
  https://bugs.kde.org/show_bug.cgi?id=373614
  https://reviews.llvm.org/D31524
  
  Please consider backporting this patch to LLVM 3.8 (or rebuilding the
- mesa package to use an LLVM version that already contains the patch).
+ mesa package to use a (much) more recent LLVM version that already
+ contains the patch).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1709399

Title:
  LLVM symbols should be versioned to avoid crashing applications that
  load mesa's swrast and also use a different libLLVM

Status in llvm-toolchain-3.8 package in Ubuntu:
  New

Bug description:
  The libgl1-mesa-dri-lts-xenial package depend on libLLVM-3.8.so.1 from
  the libllvm3.8v4 package; this library gets used when using software
  OpenGL rendering on a remote display. As a result, applications based
  on Qt5 that also use libLLVM features provided by another (newer) LLVM
  version will crash when invoked from a remote X terminal.

  Example: KDevelop5 uses libclang (and this libLLVM) for C/C++ parsing;
  I build it to use the LLVM/Clang 4.0 packages from llvm.org (and self-
  built Qt5 and KF5 libraries) and can thus not render to a remote X
  server (XQuartz on my Mac).

  There is an upstream LLVM patch which solves the issue by adding
  versioning info to libLLVM:

  https://bugs.kde.org/show_bug.cgi?id=373614
  https://reviews.llvm.org/D31524

  Please consider backporting this patch to LLVM 3.8 (or rebuilding the
  mesa package to use a (much) more recent LLVM version that already
  contains the patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1709399/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1460078] [NEW] libreoffice-kde does not provide the system (=KDE) file dialog

2015-05-29 Thread RJVB
Public bug reported:

This report concerns KUbuntu Trust 14.04.2 LTS and libreoffice
1:4.2.8-0ubuntu2 .

LibreOffice has an option (tick box) in the general settings that allows
the user to chose between LibreOffice's own file dialogs, and the
system dialogs.

When the libreoffice-kde package is not installed, this indeed works,
and one gets (what appears to be) the standard GTk file dialog for
saving, opening, etc.

As soon as libreoffice-kde is installed, one always gets the LibreOffice
dialog, regardless of the setting of this option. This degrades DE
homogeneity, and also causes a loss of features present in the KDE file
dialog but not in LibreOffice's.

Keeping libreoffice-kde uninstalled would be a workaround, but leads to
worse discomfort (very ugly and heavy UI font).

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1460078

Title:
  libreoffice-kde does not provide the system (=KDE) file dialog

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This report concerns KUbuntu Trust 14.04.2 LTS and libreoffice
  1:4.2.8-0ubuntu2 .

  LibreOffice has an option (tick box) in the general settings that
  allows the user to chose between LibreOffice's own file dialogs, and
  the system dialogs.

  When the libreoffice-kde package is not installed, this indeed works,
  and one gets (what appears to be) the standard GTk file dialog for
  saving, opening, etc.

  As soon as libreoffice-kde is installed, one always gets the
  LibreOffice dialog, regardless of the setting of this option. This
  degrades DE homogeneity, and also causes a loss of features present in
  the KDE file dialog but not in LibreOffice's.

  Keeping libreoffice-kde uninstalled would be a workaround, but leads
  to worse discomfort (very ugly and heavy UI font).

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 980153] Re: Hotplug of iMic USB soundcard does not always produce a viable audio output --Precise upgrade

2015-02-03 Thread RJVB
A few months short of THREE years later, this issue is still there in
Ubuntu 14.04 .

I see the iMic when I hotplug it, but only as a device. Pulseaudio does
not assign it to either sink or source (while the device provides both).
Using pavucontrol I do see 3 possible configurations in the
configuration tab: stereo, mono and off. But those don't serve a
purpose.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/980153

Title:
  Hotplug of iMic USB soundcard does not always produce a viable audio
  output --Precise upgrade

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  Hotplug of iMic USB soundcard does not always produce a viable audio output 
on Precise upgrade

  Steps to reproduce
  -boot up with iMic plugged in
  -unplug iMic
  -wait a minute
  -plug the iMic back in
  -select the iMic as output in the system sound preference pane

  Result
  -no audio via iMic
  -audio continues via build in speakers

  Expected results
  -audio  via iMic
  -audio via build in speakers should cut off

  
  Work around:
  Runs fine if the computer has booted with the iMic plugged in.
  or
  reboot with iMic plugged in

  
  iMic hardware details:
  Griffin Technology, Inc iMic USB audio system, the earlier model if I recall. 
 The following terminal command apparently reveal only the internal sound card.

  dmesg | grep sound
  HDA Intel SPDIF

  Both lsusb | grep audio and lsusb | grep sound don't retrieve any
  info, which is odd because the system sound preference pane lists the
  iMic device as an output.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mo25705 F pulseaudio
   /dev/snd/pcmC0D0c:   mo25705 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9840 irq 46'
 Mixer name : 'SigmaTel STAC9221 A1'
 Components : 'HDA:83847680,106b0200,00103401'
 Controls  : 23
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'system'/'Griffin Technology, Inc iMic USB audio system at 
usb-:00:1d.0-1, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB077d:07af'
 Controls  : 8
 Simple ctrls  : 6
  Date: Thu Apr 12 13:46:21 2012
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to precise on 2012-03-23 (19 days ago)
  dmi.bios.date: 10/12/06
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MBP11.88Z.0055.B08.0610121325
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F425BEC8
  dmi.board.vendor: Apple Computer, Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F425BEC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMBP11.88Z.0055.B08.0610121325:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F425BEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F425BEC8:
  dmi.product.name: MacBookPro1,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Desktop-packages] [Bug 1353892] Re: gvfsd-trash crashed with SIGABRT in g_mutex_lock()

2014-08-07 Thread RJVB
*** This bug is a duplicate of bug 125 ***
https://bugs.launchpad.net/bugs/125

On Thursday August 07 2014, rjvber...@gmail.com wrote regarding [Bug
1353892] Re: gvfsd-trash crashed with SIGABRT in g_mutex_lock()

*** This bug is a duplicate of bug 125 ***
https://bugs.launchpad.net/bugs/125

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #125, so is being marked as such.  Please
look at the other bug report to see if there is any missing information

I'd love to but that link tells me This page does not exist, or you may
not have permission to see it

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1353892

Title:
  gvfsd-trash crashed with SIGABRT in g_mutex_lock()

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  I had to kill an AppleShare mount made using the afpfs-ng package in
  my misc ppa (https://launchpad.net/~rjvbertin/+archive/ubuntu/misc).
  This crash occurred a couple of minutes later.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gvfs-daemons 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-ConKolivas-AMDFam10 3.13.11.4
  Uname: Linux 3.13.11.4-ck1-kubuntu-amdf10-rjvb x86_64
  NonfreeKernelModules: ufsd zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Aug  7 09:33:07 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2014-05-03 (95 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.111 
/org/gtk/gvfs/exec_spaw/1
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-trash crashed with SIGABRT in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk floppy fuse lpadmin plugdev 
sambashare sudo video

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1353892] Re: gvfsd-trash crashed with SIGABRT in g_mutex_lock()

2014-08-07 Thread RJVB
*** This bug is a duplicate of bug 125 ***
https://bugs.launchpad.net/bugs/125

What's the point in asking me to check a report to which I don't have
access?!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1353892

Title:
  gvfsd-trash crashed with SIGABRT in g_mutex_lock()

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  I had to kill an AppleShare mount made using the afpfs-ng package in
  my misc ppa (https://launchpad.net/~rjvbertin/+archive/ubuntu/misc).
  This crash occurred a couple of minutes later.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gvfs-daemons 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-ConKolivas-AMDFam10 3.13.11.4
  Uname: Linux 3.13.11.4-ck1-kubuntu-amdf10-rjvb x86_64
  NonfreeKernelModules: ufsd zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Aug  7 09:33:07 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2014-05-03 (95 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.111 
/org/gtk/gvfs/exec_spaw/1
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-trash crashed with SIGABRT in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk floppy fuse lpadmin plugdev 
sambashare sudo video

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp