[Desktop-packages] [Bug 1793304] [NEW] package libglib2.0-dev 2.48.2-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: This is likely an issue to do with having both python2.7 and 3.5 on the machine. The work around is the same as that I gave for samba in Bug 1651660. TL:DR Copy weakref.py from the 3.5 directory to the 2.7 directory and edit syntax until offender installs Patched weakref.py uploaded to the above mentioned bug. The root of the problem is likely either the QGIS 3.2 repo install or the Paraview 5.5 binary copy. Cheers Kim ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Sep 19 20:27:49 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-12-10 (648 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1793304 Title: package libglib2.0-dev 2.48.2-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glib2.0 package in Ubuntu: New Bug description: This is likely an issue to do with having both python2.7 and 3.5 on the machine. The work around is the same as that I gave for samba in Bug 1651660. TL:DR Copy weakref.py from the 3.5 directory to the 2.7 directory and edit syntax until offender installs Patched weakref.py uploaded to the above mentioned bug. The root of the problem is likely either the QGIS 3.2 repo install or the Paraview 5.5 binary copy. Cheers Kim ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Sep 19 20:27:49 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-12-10 (648 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1793304/+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 1210280] Re: libgtop2 used by system monitor reporting incorrect number of processors for Ubuntu 13.10 vms on Hyper-V
This is still an issue for 16.04 and an 80 "core" system. SysInfo only shows 72 cores while lscpu shows 80. As an aside the layout of the SysInfo GUI could do with a workover. For 4 CPUs it is fine but after that it starts to get very red. I have 3 machines with dual hexacores and 2 machines with quad decacores all hyperthreaded and all running 16.04 as workstations to do crunching. In SysInfo on the quad decacore machines the CPU usage graph is ~8mm high and all I can see is red. Allowing components of the performance display to be rescaled and to distribute the rainbow more evenly from CPU#1 to CPU#n would be a worthwhile improvement. The comments in libgtop3 before defining GLIBTOP_NCPU sound like you don't think we should be using Ubuntu for real work - use the RH/SUSE lineage instead - not all of us are gamers using domestic machines;-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgtop2 in Ubuntu. https://bugs.launchpad.net/bugs/1210280 Title: libgtop2 used by system monitor reporting incorrect number of processors for Ubuntu 13.10 vms on Hyper-V Status in libgtop: Confirmed Status in libgtop2 package in Ubuntu: Incomplete Status in libgtop2 source package in Saucy: Won't Fix Bug description: We have noticed that when a Ubuntu 13.10 VM is configured with 64CPUs on Hyper-V, system monitor only shows 32 CPUs. This bug is also observed on Ubuntu 12.04. So it seems like an old issue. Please provide a fix. Attached are two files - One of the files is the output from system monitor and the other one contains the output from lscpu. System monitor output shows 32 CPUs whereas lscpu output shows the 64 CPUs correctly. Please let me know if you need more info. Thanks, Abhishek To manage notifications about this bug go to: https://bugs.launchpad.net/libgtop/+bug/1210280/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
It appears to be fixed now though, either that or the alsamixer fix is now sticky. If it doesn't work out of the box then do an update and if that doesn't work try the alsamixer fix and it should then continue to work after reboot. -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
I just realised my Yes was a ambiguous. Yes it still exists and has not been fixed on 16.04.1. -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)
Yes. On a Dell t610. Same symptoms as above. Soundcard works fine on CentOS 6 live so hardware is OK -- 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/1551385 Title: No sound on ASUS Xonar DGX Soundcard (16.04) Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. Tested with the app to test speakers, Firefox, VLC, and checked with pavucontrol, the progress bar indicate that a sound is played on the card, but no sound on the speakers. I report this bug because it works on the same version with the integrated card of my motherboard. (ASUS H87-PLUS) On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all defaults params) The speakers connected are the Logitech Z9600 (by 3 jacks), and I precise that they are correctly plugged in, etc..., it works when I connect it to the integrated sound card of my motherboard (and if I use Ubuntu 14.04 LTS) I don't know if it's a normal development bug, but in doubt I report it. Thank you, Valentin Crône To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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
