[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: In Progress Status in maas package in Ubuntu: Invalid Bug description: If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main
Maybe we can have `journalctl-grep` package for administrators that use this grep functionality for checking what happened? Nowadays debugging is recognized as foremost computing activity, even chips have special JTAG pins to allow online debugging. I could expect most of the system administrators with big logs would appreciate faster searching of log files thanks to `journalctl -g` in the leading cloud operating system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751006 Title: Journalctl compiled without pattern matching support, pcre2 is not in main Status in pcre2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Please add pattern matching support to journalctl. At the moment, the -g (--grep) option as described in the man page doesn't work: ╰─▶ journalctl --grep=xhci-hcd Compiled without pattern matching support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1751006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785699] Re: Invisible text in insenstitive suggested action buttons
** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1785699 Title: Invisible text in insenstitive suggested action buttons Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: Impact -- The suggestion action button does not have correct text styling when the action button is "insensitive" (greyed out). This makes the text basically invisible since it has the same dark grey color for both the foreground text and the background. Test Case 1 --- 1. Open the file browser. 2. Open the ☰ menu and select New Folder. What happens: 1. In the New Folder dialog, the top right button has invisible text. Screenshot attached. What should happen: It should show the word Create but greyed out. Test Case 2 --- 1. Open the gedit text editor. 2. Open the ☰ menu and select Save As. 3. In the Name field, delete all the text to make the field empty. What happens: The word Save in the top right button becomes invisible. Other Info -- Ubuntu 18.04.1 LTS light-themes 16.10+18.04.20180421.1-0ubuntu1 Ambiance theme libgtk-3-0 3.22.30-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1785699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working
That last link has moved. It's now: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1783200 Title: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working Status in pulseaudio package in Ubuntu: Incomplete Bug description: I believe this is a pulseaudio regression, as the output of alsa-info (http://www.alsa- project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine as far as I can see. I'm currently running Ubuntu 18.04, and I believe this is a regression as audio used to work under 17.10. Since upgrading (which fixed a good number of other incompatibilities with the machine), I've had no luck getting audio to work at all. I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and 'pulseaudio -vv'. If I can provide any other information, or if there's anything you'd like me to try, I'd be happy to help in any way possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server
I've tested this in a minimal image and it appears to work as designed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: In Progress Status in maas package in Ubuntu: Invalid Bug description: If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785723] [NEW] Memory leak in systemd-journald
Public bug reported: systemd-journald has 144 MiB resident after 35 days. After a reboot this drops to 23 MiB. All logging config is stock except that logs rotate monthly, and the machine is not used as a syslog server. This is a very lightly loaded web and mail server, < 10 requests per hour. /var/log/journal/.../system.journal grows by 10-15 MiB per day, mostly logging automated attacks against SSH, SMTP, and random ports. The journal daemon uses more memory than all other daemons combined. I sure hope this is a leak and not by design ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 6 22:54:34 2018 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=5de0cac7-17b6-4a0f-8715-54cfaaa0a9a9 ro console=tty1 console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1785723 Title: Memory leak in systemd-journald Status in systemd package in Ubuntu: New Bug description: systemd-journald has 144 MiB resident after 35 days. After a reboot this drops to 23 MiB. All logging config is stock except that logs rotate monthly, and the machine is not used as a syslog server. This is a very lightly loaded web and mail server, < 10 requests per hour. /var/log/journal/.../system.journal grows by 10-15 MiB per day, mostly logging automated attacks against SSH, SMTP, and random ports. The journal daemon uses more memory than all other daemons combined. I sure hope this is a leak and not by design ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 6 22:54:34 2018 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=5de0cac7-17b6-4a0f-8715-54cfaaa0a9a9 ro console=tty1 console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server
Here is my proposed patch. ** Changed in: maas (Ubuntu) Status: Confirmed => Invalid ** Package changed: cloud-init (Ubuntu) => base-files (Ubuntu) ** Changed in: base-files (Ubuntu) Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) ** Changed in: base-files (Ubuntu) Status: Confirmed => In Progress ** Patch added: "my patch" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+attachment/5172355/+files/base-files_10.1ubuntu4_10.1ubuntu5.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: In Progress Status in maas package in Ubuntu: Invalid Bug description: If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1134036] [NEW] Failure when using ssh with a locale that is not configured on the server
You have been subscribed to a public bug: If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set ** Affects: base-files (Ubuntu) Importance: Medium Status: Confirmed ** Affects: maas (Ubuntu) Importance: Medium Status: Invalid ** Tags: id-5b21b1006874c4e4159dea3f -- Failure when using ssh with a locale that is not configured on the server https://bugs.launchpad.net/bugs/1134036 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 485480] Re: cups converts multiple times between pdf and ps
Hi G, thanks for your reply. I have tried to reproduce case 3 (as I believe this is the one most interdependent from other applications/libs as Poppler or KDE-/Qt) using an EPSON BX620FWD. The problem described above did not occour. My printer at that time was a Brother DCP-120C, but I don't have this device any more. So either the problem is solved or it is specific to Brother printers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/485480 Title: cups converts multiple times between pdf and ps Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups I guess this bug could be related to bug #382379 but as I'm not really shure I didn't append to that pretty overloaded bug. Printing a PDF can take very long (and I'm not shure if the print jobs really end successfully). I have tried three cases: CASE 1: I have a PDF (a converted PowerPoint presentation, about 125 slides, 10 MB). The PDF mainly consists of text, formula and vector graphics. There are a few JPGs in it, too, but they are low resolution only. As more than 120 pages is very much to print and the font size is big, too, I wanted to print 2 slides on one DIN A4 page. Okular (or kprinter?) has a function for this so I tried to use it. After about 1 hour I didn't have at least one printed page but a CPU intensive gs process running and a temporary PS file that was far bigger than 200 MB. After some more waiting I cancelled the printing job. CASE 2: I had the suspicion that gs processed each file as seperate image to fit two of them on one page. So I tried Adobe reader togive out a ps file with 2 slides on one page hoping that this application is a bit more efficient. It really is more efficient and the resulting PS file was "just" about 130 MB which I guess is not too bad if the Reader has converted some vector grafics into rasterized images (for compatibility reasons for example). I expected it should be no big problem to print out this "printer ready" PS file... So I opened in Okular and tried to print it. But after some time the printing wasn't even started and it took a closer look at the processes running: $ ps -fA | grep gs lp3991 2481 0 19:27 ?00:00:00 /bin/sh /usr/lib/cups/filter/pstopdf 433 dominic Physik 1_1 1 [...] /var/spool/cups/d00433-001 lp3992 2481 0 19:27 ?00:00:00 Brother_DCP-120C 433 dominic Physik 1_1 1 BRColorEnhancement=ON [...] lp3993 2481 0 19:27 ?00:00:00 /bin/sh /usr/lib/cups/filter/cpdftocps 433 dominic Physik 1_1 1 BRColor[...] lp3994 2481 0 19:27 ?00:00:00 /bin/csh /usr/lib/cups/filter/brlpdwrapperDCP110C 433 dominic Physik 1_1 1 [...] root 3995 2481 0 19:27 ?00:00:00 usb://Brother/DCP-120C 433 dominic Physik 1_1 1 [...] lp4058 3991 61 19:28 ?00:00:07 gs -dSAFER -dCompatibilityLevel=1.3 -dAutoRotatePages=/None -dAutoFilterColorImages=false -dNOPLATFONTS -dPARANOIDSAFER -sstdout=%stderr -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/printer -dDoNumCopies -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr -sOutputFile=- -dSAFER -dCompatibilityLevel=1.3 -dAutoRotatePages=/None -dAutoFilterColorImages=false -dNOPLATFONTS -dPARANOIDSAFER -sstdout=%stderr -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/printer -dDoNumCopies -c .setpdfwrite -f - (Cups is process 2481) So it seems as if the printer ready PS file is converted to PDF and back to PS again by Cups and that gs is processing it in some way, too. This semed very inefficeinto me so I canceled the printing job again as it probably wouldn't be processed any time soon. CASE 3: I thought maybe Okular and Cups couldn't communicate that the file was already ready for printing. So I tried to print the file directly using "lp" - but the problem was the same. And also printing diectly from Adobe Reader had this effect (but I guess this is hardly surprising as it seems to use "lpr"). -- Maybe the problem is something completely different, but that's all I could find out. The only thing I know for sure is that I have no proper solution to print such documents which I need for studying :-( But I hope that this bug can be solved. I will help as good as I can. ProblemType: Bug Architecture: i386 Date: Thu Nov 19 20:08:19 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Brother_DCP-120C: usb://Brother/DCP-120C device for PDF: cups-pdf:/ device for PDF1: cups-pdf:/ NonfreeKernelModules: nvidia Package: cups 1.4.1-5ubuntu2.1 Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Brother_DCP-120C: Brother DCP-110C CUPS v1.1 PDF1: Generic CUPS-PDF Printer ProcCmdLine: root=UUID=372d1bf0-e370-4a49-8e93-2e7ef4662923 ro quiet splash
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
found this page looking for information for same model laptop running Manjaro, also confirmed sound working on windows 10 found another page for ALC294 codec - https://askubuntu.com/questions/986140/no-sound-output-ubuntu-17-10-asus-zenbook-13 all 3 appear to have common problem caused by windows 10 shutdown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785720] [NEW] Built-In Analog Audio Low & Distorted
Public bug reported: I've been having trouble with my sound since I installed Ubuntu 18.04.1 LTS. The sound from my graphics card via the HDMI monitor is fine, but the internal Intel HDA audio is very low, distorted and crackling, both for headphones and speakers (green front / green back). I've spent many hours so far and tried a number of suggestions such as: Looking in Alsa Mixer for sound levels Adding "options snd-hda-intel position_fix=1" to the end of my /etc/modprobe.d/alsa-base.conf Issuing something like pulseaudio -k && rm -r ~/.config/pulse I've also followed the instructions here: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS But that didn't seem to help either The devices are all listed, and via pavucontrol I can see the audio bars moving and the sound levels seem fine In Windows, my sound device driver is SoundBlaster Recon3Di, if that helps at all? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brett 1769 F pulseaudio /dev/snd/pcmC0D0c: brett 1769 F...m pulseaudio /dev/snd/pcmC0D0p: brett 1769 F...m pulseaudio /dev/snd/controlC0: brett 1769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 18:36:34 2018 InstallationDate: Installed on 2018-06-01 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2018 dmi.bios.vendor: Alienware dmi.bios.version: A13 dmi.board.name: 0FRTKJ dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA13:bd02/09/2018:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0FRTKJ:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Alienware Area-51 R2 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-06T18:13:00.717349 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1785720 Title: Built-In Analog Audio Low & Distorted Status in alsa-driver package in Ubuntu: New Bug description: I've been having trouble with my sound since I installed Ubuntu 18.04.1 LTS. The sound from my graphics card via the HDMI monitor is fine, but the internal Intel HDA audio is very low, distorted and crackling, both for headphones and speakers (green front / green back). I've spent many hours so far and tried a number of suggestions such as: Looking in Alsa Mixer for sound levels Adding "options snd-hda-intel position_fix=1" to the end of my /etc/modprobe.d/alsa-base.conf Issuing something like pulseaudio -k && rm -r ~/.config/pulse I've also followed the instructions here: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS But that didn't seem to help either The devices are all listed, and via pavucontrol I can see the audio bars moving and the sound levels seem fine In Windows, my sound device driver is SoundBlaster Recon3Di, if that helps at all? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brett 1769 F pulseaudio /dev/snd/pcmC0D0c: brett 1769 F...m pulseaudio /dev/snd/pcmC0D0p: brett 1769 F...m pulseaudio /dev/snd/controlC0: brett 1769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 18:36:34 2018 InstallationDate: Installed on 2018-06-01 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH
Re: [Touch-packages] [Bug 1302192] Re: capabilities not preserved on installation
Well, you could even enable ping capabilities by unpriviledged users with the ICMP socket type: # sysctl -w net.ipv4.ping_group_range='0 65536' $ strace -esocket ping 127.0.0.1 socket(AF_INET, SOCK_DGRAM, IPPROTO_ICMP) = 3 Regards, On Mon, Aug 6, 2018 at 10:30 PM Launchpad Bug Tracker <1302...@bugs.launchpad.net> wrote: > > This bug was fixed in the package livecd-rootfs - 2.534 > > --- > livecd-rootfs (2.534) cosmic; urgency=medium > > [ Michael Hudson-Doyle ] > * Disable journald rate limiting in the live-server live session. > (LP: #1776891) > > [ Steve Langasek ] > * generate all tar files with --xattrs. LP: #1302192. > > -- Steve Langasek Mon, 06 Aug 2018 > 13:12:02 -0700 > > ** Changed in: livecd-rootfs (Ubuntu) >Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1302192 > > Title: > capabilities not preserved on installation > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302192] Re: capabilities not preserved on installation
This bug was fixed in the package livecd-rootfs - 2.534 --- livecd-rootfs (2.534) cosmic; urgency=medium [ Michael Hudson-Doyle ] * Disable journald rate limiting in the live-server live session. (LP: #1776891) [ Steve Langasek ] * generate all tar files with --xattrs. LP: #1302192. -- Steve Langasek Mon, 06 Aug 2018 13:12:02 -0700 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782802] Re: ditch ipconfig in favor of dhclient -4 in 18.10
Well there are quite a few uploads to choose from, but this one https://git.launchpad.net/ubuntu/+source/initramfs- tools/tree/scripts/functions?id=import/0.125ubuntu6#n339 is about the least "ipconfig-y" and it still calls it sometimes... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1782802 Title: ditch ipconfig in favor of dhclient -4 in 18.10 Status in initramfs-tools package in Ubuntu: New Bug description: When adding ipv6 netboot support to initramfs-tools in yakkety/zesty, this was initially attempted with replacing ipconfig with dhclient. As described in LP: #1621507, the use of dhclient for ipv4 dhcp was backed out in favor of ipconfig. So at the moment, we are using both ipconfig from klibc-utils and dhclient from isc-dhcp-client in the initramfs. We want to switch off of klibc-utils completely and use isc-dhcp- client for both ipv4 and ipv6 in initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] Re: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1785498, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1785498 g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in aptitude package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: appstream (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in appstream package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in appstream package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] Re: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Also affects: aptitude (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in aptitude package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] [NEW] appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Public bug reported: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Attachment added: "aptitude.png" https://bugs.launchpad.net/bugs/1785703/+attachment/5172303/+files/aptitude.png ** Description changed: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) + + https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in glib2.0 package in Ubuntu: New Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 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/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785475] Re: Scrolling in files gives display isues
arcording ubuntu-bug TERM=xterm but it doesn't matter. I didn't fiddle THe problem is there even via console tty1 or ssh session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: Confirmed Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1785475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 519971] Re: HP 5610 Checking ink levels fails
Hi Esther. Thanks for the update and the extra info. I'll look at next steps. And I'll try to find duplicates for this no-ink-levels issue. Take care :) G ** Changed in: cups (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/519971 Title: HP 5610 Checking ink levels fails Status in cups package in Ubuntu: New Bug description: Binary package hint: cups system-config-printer 1.1.12 HP Officejet 5610 All-in-One Ubuntu 9.10 Karmic Koala I knew my ink levels were low, but not certain. I launched the printer properties box, navigated to the ink/toner levels window. The window reports that marker levels are not reported for this printer and no status messages. Hitting the refresh button returns a CUPS error message, "CUPS server error: There was an error during the CUPS operation: 'client-error-document-format-not-supported'." I would have expected the ink levels to be reported when hitting the refresh button. But before that, I would have expected the ink levels to already be reported when opening the configuration property window. ProblemType: Bug Architecture: i386 CheckboxSubmission: fd057b0bdea60eb17cdbf0a26f3fba5f CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948 CupsErrorLog: E [10/Feb/2010:09:49:36 -0700] Returning IPP client-error-document-format-not-supported for Print-Job (ipp://localhost/printers/Officejet_5600_series) from localhost Date: Wed Feb 10 10:23:19 2010 DistroRelease: Ubuntu 9.10 Lpstat: device for Officejet_5600_series: hpfax:/usb/Officejet_5600_series?serial=CN5CRDF7M804CY device for Officejet_5600_series_fax: hpfax:/usb/Officejet_5600_series?serial=CN5CRDF7M804CY Lsusb: Bus 003 Device 002: ID 03f0:4f11 Hewlett-Packard OfficeJet 5600 (USBHUB) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. MS-7145 Package: cups 1.4.1-5ubuntu2.1 Papersize: letter PpdFiles: Officejet_5600_series: HP Officejet 5600 Series hpijs, 3.9.8 Officejet_5600_series_fax: HP Fax hpijs ProcCmdLine: root=UUID=f86bcd21-a135-45c3-a637-a151c5920915 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: cups Uname: Linux 2.6.31-19-generic i686 XsessionErrors: (gnome-settings-daemon:1683): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:1775): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:1780): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-panel:1774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 27 dmi.bios.date: 06/07/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7145 dmi.board.vendor: MSI dmi.board.version: 200 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd06/07/2005:svnToBeFilledByO.E.M.:pnMS-7145:pvr0A:rvnMSI:rnMS-7145:rvr200:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7145 dmi.product.version: 0A dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/519971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785475] Re: Scrolling in files gives display isues
Please answer also the other questions: which terminal, and the full output of 'locale'. Further, did you fiddle with your system? Have you symlinked some libraries? Also, are you able to build nano from source? If so, please try building the latest 2.9.8, and see how it fares. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: Confirmed Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1785475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785683] Re: dep8 tests fail on non-intel
** Branch linked: lp:software-properties -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1785683 Title: dep8 tests fail on non-intel Status in software-properties package in Ubuntu: Confirmed Bug description: According to proposed migration https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html Software-properties tests have 'Always failed' on arch other than intel. This failure is not specific to dep8 but rather can be seen just by running the unit tests. In a fresh non-intel container: (launched with 'lxc launch ubuntu-daily:cosmic c1' on ppc64 host) % apt-get update -q && apt-get build-dep -y software-properties % apt-get install bzr --no-install-recommends % bzr branch lp:software-properties % cd software-properties ## taken from debian/tests/run-tests % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests/test*.py Or just run the failing test: % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest \ tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources $ LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources software-properties (0.96.24.36 to 0.96.26) Maintainer: Michael Vogt 3 days old autopkgtest for crash/7.2.3+real-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for livecd-rootfs/2.533: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for software-properties/0.96.26: amd64: Pass, arm64: Always failed, armhf: Always failed, i386: Pass, ppc64el: Always failed, s390x: Always failed Valid candidate ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-common 0.96.24.36 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic ppc64le ApportVersion: 2.20.10-0ubuntu7 Architecture: ppc64el Date: Mon Aug 6 17:20:32 2018 PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 ProcLoadAvg: 0.15 0.11 0.08 1/2275 21089 ProcLocks: 9: POSIX ADVISORY WRITE 187 00:3c:129 0 EOF 14: FLOCK ADVISORY WRITE 193 00:3c:143 0 EOF ProcSwaps: Filename TypeSizeUsedPriority nonevirtual 8388544 8388544 0 ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-015) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #31-Ubuntu SMP Tue Jul 17 15:37:15 UTC 2018 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1785683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1067434] Re: Sound output device keeps changing when using headphones
Problem reappeared for me since Linux Mint 18. I now run LM 19 Mate and again, problem is there. I can see the sound fluctuating in Sound Preferences / Input and pavucontrol / Output Devices and alsamixer. In alsamixer, my loopback is already disabled so it's not a solution for me. For an unknown reason, the hda-task-rejack solution is not working anymore, after a reboot, the changes are gone. It's like it's never being saved after clicking "Install boot override". My last solution is to leave a jack cable into the front microphone of my desktop tower which solve the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1067434 Title: Sound output device keeps changing when using headphones Status in alsa-driver package in Ubuntu: Expired Bug description: Recently upgraded to 12.10. Having issues with sound when using headphones plugged into the front ports. Something that doesn't happen when booting to windows - so fairly confident it's an Ubuntu issue. When listening to any sound, music, video etc the sound levels jump up and down and click. If I open "sound" from the settings menu when playing videos or music and viewing the "output" tab I can see "headphone - built-in audio disappear and reappear (very quickly) so I'm guessing the system is jumping back to the "analogue output" and back again which is why the sound volume changes and clicks. Worth noting I never used my headphones when 12.04 was installed so not sure if it's this OS or Ubuntu hates my hardware generally. Booted from live cd (usb) to 12.04 and there wasnt any issue. Anyone seen this before? any advice? Sound is built in to motherboard. I have the Gigabyte GA-X58A-UD5. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Tue Oct 16 18:07:44 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-09-29 (17 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1067434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785683] Re: dep8 tests fail on non-intel
** Branch linked: lp:~smoser/software-properties/trunk.fix-tests-non- intel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1785683 Title: dep8 tests fail on non-intel Status in software-properties package in Ubuntu: Confirmed Bug description: According to proposed migration https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html Software-properties tests have 'Always failed' on arch other than intel. This failure is not specific to dep8 but rather can be seen just by running the unit tests. In a fresh non-intel container: (launched with 'lxc launch ubuntu-daily:cosmic c1' on ppc64 host) % apt-get update -q && apt-get build-dep -y software-properties % apt-get install bzr --no-install-recommends % bzr branch lp:software-properties % cd software-properties ## taken from debian/tests/run-tests % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests/test*.py Or just run the failing test: % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest \ tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources $ LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources software-properties (0.96.24.36 to 0.96.26) Maintainer: Michael Vogt 3 days old autopkgtest for crash/7.2.3+real-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for livecd-rootfs/2.533: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for software-properties/0.96.26: amd64: Pass, arm64: Always failed, armhf: Always failed, i386: Pass, ppc64el: Always failed, s390x: Always failed Valid candidate ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-common 0.96.24.36 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic ppc64le ApportVersion: 2.20.10-0ubuntu7 Architecture: ppc64el Date: Mon Aug 6 17:20:32 2018 PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 ProcLoadAvg: 0.15 0.11 0.08 1/2275 21089 ProcLocks: 9: POSIX ADVISORY WRITE 187 00:3c:129 0 EOF 14: FLOCK ADVISORY WRITE 193 00:3c:143 0 EOF ProcSwaps: Filename TypeSizeUsedPriority nonevirtual 8388544 8388544 0 ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-015) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #31-Ubuntu SMP Tue Jul 17 15:37:15 UTC 2018 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1785683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 557818] Re: cups-client does not create /etc/cups directory, let alone client.conf
Hi Daniel. Thanks for the update and the cups info. I'll look at next steps. Take care :) G -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/557818 Title: cups-client does not create /etc/cups directory, let alone client.conf Status in cups package in Ubuntu: New Bug description: Binary package hint: cups-client This concerns cups-client 1.4.2-10 in Lucid beta1. When you install the cups-client package, there is no sign whatsoever of the all-important /etc/cups/client.conf file; even the /etc/cups directory is not present. The package should install a client.conf file, with helpful comments therein, as is customary for other client-type programs (e.g. dumb MTAs). This is particularly relevant for sites that use a central CUPS server (i.e. the "cups" package is not locally installed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/557818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1280766] Re: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
Thanks William. Closing by marking "Invalid" as VIM and Ubuntu versions now both EOL. ** Changed in: vim (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1280766 Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in vim package in Ubuntu: Invalid Bug description: Ubuntu 12.4 arm trying to install/purge/remove vim returns errors each time. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: vim 2:7.3.429-2ubuntu2.1 Uname: Linux 3.0.35-gbe699c6-dirty armv7l ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: vim: Purge Architecture: armel Date: Sun Feb 16 12:44:05 2014 DpkgTerminalLog: Removing vim ... update-alternatives: error: /var/lib/dpkg/alternatives/rvim corrupt: line not terminated while trying to read status dpkg: error processing vim (--purge): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:vim:2:7.3.429-2ubuntu2.1:subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 MarkForUpload: True SourcePackage: vim Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2014-02-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1280766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785683] [NEW] dep8 tests fail on non-intel
Public bug reported: According to proposed migration https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html Software-properties tests have 'Always failed' on arch other than intel. This failure is not specific to dep8 but rather can be seen just by running the unit tests. In a fresh non-intel container: (launched with 'lxc launch ubuntu-daily:cosmic c1' on ppc64 host) % apt-get update -q && apt-get build-dep -y software-properties % apt-get install bzr --no-install-recommends % bzr branch lp:software-properties % cd software-properties ## taken from debian/tests/run-tests % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests/test*.py Or just run the failing test: % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest \ tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources $ LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources software-properties (0.96.24.36 to 0.96.26) Maintainer: Michael Vogt 3 days old autopkgtest for crash/7.2.3+real-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for livecd-rootfs/2.533: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for software-properties/0.96.26: amd64: Pass, arm64: Always failed, armhf: Always failed, i386: Pass, ppc64el: Always failed, s390x: Always failed Valid candidate ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-common 0.96.24.36 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic ppc64le ApportVersion: 2.20.10-0ubuntu7 Architecture: ppc64el Date: Mon Aug 6 17:20:32 2018 PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 ProcLoadAvg: 0.15 0.11 0.08 1/2275 21089 ProcLocks: 9: POSIX ADVISORY WRITE 187 00:3c:129 0 EOF 14: FLOCK ADVISORY WRITE 193 00:3c:143 0 EOF ProcSwaps: Filename TypeSizeUsedPriority nonevirtual8388544 8388544 0 ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-015) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #31-Ubuntu SMP Tue Jul 17 15:37:15 UTC 2018 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 ** Affects: software-properties (Ubuntu) Importance: Medium Assignee: Scott Moser (smoser) Status: Confirmed ** Tags: apport-bug cosmic ppc64el uec-images ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1785683 Title: dep8 tests fail on non-intel Status in software-properties package in Ubuntu: Confirmed Bug description: According to proposed migration https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html Software-properties tests have 'Always failed' on arch other than intel. This failure is not specific to dep8 but rather can be seen just by running the unit tests. In a fresh non-intel container: (launched with 'lxc launch ubuntu-daily:cosmic c1' on ppc64 host) % apt-get update -q && apt-get build-dep -y software-properties % apt-get install bzr --no-install-recommends % bzr branch lp:software-properties % cd software-properties ## taken from debian/tests/run-tests % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests/test*.py Or just run the failing test: % LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest \ tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources $ LC_ALL=C.UTF-8 xvfb-run -e "/tmp/xvfb.log" python3 -m unittest tests.test_dbus.TestDBus.test_enable_enable_disable_source_code_sources software-properties (0.96.24.36 to 0.96.26) Maintainer: Michael Vogt 3 days old autopkgtest for crash/7.2.3+real-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for livecd-rootfs/2.533: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass autopkgtest for software-properties/0.96.26: amd64: Pass, arm64: Always failed, armhf: Always failed, i386: Pass, ppc64el: Always failed, s390x: Always failed Valid candidate ProblemType: Bug DistroRelease: Ubuntu 18.10 Package:
[Touch-packages] [Bug 1280766] Re: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
Yes I think it can be closed. I just thought it was serious at the time, because vim is quite important. I see that problem was with an armel version, which is probably solved by now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1280766 Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: Ubuntu 12.4 arm trying to install/purge/remove vim returns errors each time. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: vim 2:7.3.429-2ubuntu2.1 Uname: Linux 3.0.35-gbe699c6-dirty armv7l ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: vim: Purge Architecture: armel Date: Sun Feb 16 12:44:05 2014 DpkgTerminalLog: Removing vim ... update-alternatives: error: /var/lib/dpkg/alternatives/rvim corrupt: line not terminated while trying to read status dpkg: error processing vim (--purge): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:vim:2:7.3.429-2ubuntu2.1:subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 MarkForUpload: True SourcePackage: vim Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2014-02-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1280766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782802] Re: ditch ipconfig in favor of dhclient -4 in 18.10
Which cases were still using ipconfig and why? Can you point to the exact upload you're looking at? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1782802 Title: ditch ipconfig in favor of dhclient -4 in 18.10 Status in initramfs-tools package in Ubuntu: New Bug description: When adding ipv6 netboot support to initramfs-tools in yakkety/zesty, this was initially attempted with replacing ipconfig with dhclient. As described in LP: #1621507, the use of dhclient for ipv4 dhcp was backed out in favor of ipconfig. So at the moment, we are using both ipconfig from klibc-utils and dhclient from isc-dhcp-client in the initramfs. We want to switch off of klibc-utils completely and use isc-dhcp- client for both ipv4 and ipv6 in initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
** This bug is no longer a duplicate of private bug 1710637 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1217495] Re: I am getting the same error - tried the suggested solutions
intrader, Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates. It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal: apport-collect 1217495 and add any additional information that you think relevant. Alternatively, please confirm that this is no longer a problem and that we can close the report. If we do not hear from you the bug report will close itself in approximately two months time. Thank you again for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1217495 Title: I am getting the same error - tried the suggested solutions Status in vim package in Ubuntu: Incomplete Bug description: hello, it was after I upgrade my ubuntu 12.04. And now when I start gvim in the terminal .It will return the following message: gvim:9055): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible (gvim:9055): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `' ... I hage used sudo gconftool-2 --type bool --set /desktop/gnome/interface/accessibility false as suggested, and reinstalled gvim. Still continue to have errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1217495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504827] Re: vimtutor opens up empty
Jerome, Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates. It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal: apport-collect 1504827 and add any additional information that you think relevant. Alternatively, please confirm that this is no longer a problem and that we can close the report. If we do not hear from you the bug report will close itself in approximately two months time. Thank you again for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1504827 Title: vimtutor opens up empty Status in vim package in Ubuntu: Incomplete Bug description: bubba@mine:~$ vimtutor The program 'vimtutor' is currently not installed. You can install it by typing: sudo apt-get install vim-runtime bubba@mine:~$ which vim bubba@mine:~$ which vi /usr/bin/vi bubba@mine:~$ dpkg-query -S $(which vi) dpkg-query: no path found matching pattern /usr/bin/vi bubba@mine:~$ vi ~ ~ ~ VIM - Vi IMproved ~ ~ version 7.4.488 ~ by Bram Moolenaar et al. ~ Modified by pkg-vim-maintain...@lists.alioth.debian.org ~ Vim is open source and freely distributable ~ ~Become a registered Vim user! ~type :help register for information ~ ~type :q to exit ~type :help orfor on-line help ~type :help version7 for version info ~ ~Running in Vi compatible mode ~type :set nocpfor Vim defaults ~type :help cp-default for info on this ~ ~ ~ :q bubba@mine:~$ dpkg-query -l 'vi*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= un vile (no description available) ii vile-common9.8p-1 all VI Like Emacs - support files for ii vile-filters 9.8p-1 amd64VI Like Emacs - highlighting filt un vim (no description available) un vim-athena (no description available) ii vim-common 2:7.4.488-3u amd64Vi IMproved - Common files un vim-gnome(no description available) un vim-gtk (no description available) un vim-nox (no description available) ii vim-tiny 2:7.4.488-3u amd64Vi IMproved - enhanced vi editor un virtualbox-gue (no description available) bubba@mine:~$ sudo apt-get install vim-runtime Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: vim-runtime 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 4,980 kB of archives. After this operation, 26.2 MB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu/ vivid/main vim-runtime all 2:7.4.488-3ubuntu2 [4,980 kB] Fetched 4,980 kB in
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
This isn't a bug but a major feature of wayland: If you have root rights you no more get access to the graphical user interface which makes it harder for a gui application to spy on another application's keyboard input. The backdraw of this is that every application that needs root rights for its work has to be re-written to have 2 parts: - the actual gui application and - a small helper that gets root access using pkgkit The second advantage of this security measure is that now no more the whole application that might suffer from security flaws has root access, but only the part that really needs root rights. td;lr: The fact that gui applications no more run when given root rights won't change. It is the applications that have to adapt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as
[Touch-packages] [Bug 1675141] Re: lightdm crashed with SIGSEGV in munmap()
Five identical bugs have been autoduplicated to here: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1700391 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1720474 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1744450 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756632 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1761702 All are "lightdm crashed with SIGSEGV in _dl_fini()" rather than munmap() If these are not the same bug then those 5 should be merged and unduplicated from this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1675141 Title: lightdm crashed with SIGSEGV in munmap() Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Bug description: didn't notice anything except that message that I had a bug to report... ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: lightdm 1.21.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Wed Mar 22 20:03:09 2017 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2017-03-16 (6 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170316) LightdmConfig: [Seat:*] autologin-guest=false autologin-user=ben autologin-user-timeout=0 ProcCmdline: lightdm --session-child 13 16 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) Signal: 11 SourcePackage: lightdm StacktraceTop: munmap () at ../sysdeps/unix/syscall-template.S:84 _dl_unmap_segments (l=l@entry=0x55eb13fedb40) at ./dl-unmap-segments.h:32 _dl_unmap (map=map@entry=0x55eb13fedb40) at ../sysdeps/x86_64/tlsdesc.c:140 _dl_close_worker (map=map@entry=0x55eb13fedb40, force=force@entry=false) at dl-close.c:678 _dl_close_worker (force=false, map=0x55eb13fedb40) at dl-close.c:125 Title: lightdm crashed with SIGSEGV in munmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1675141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700391] Re: lightdm crashed with SIGSEGV in _dl_fini()
*** This bug is a duplicate of bug 1675141 *** https://bugs.launchpad.net/bugs/1675141 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1700391 Title: lightdm crashed with SIGSEGV in _dl_fini() Status in lightdm package in Ubuntu: Confirmed Bug description: just logged in... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: lightdm 1.22.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 Date: Sun Jun 25 06:56:06 2017 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2017-06-13 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) ProcCmdline: lightdm --session-child 13 20 ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f42f7623f29 <_dl_fini+777>: mov0x8(%rax),%r12 PC (0x7f42f7623f29) ok source "0x8(%rax)" (0x7f42f1b2cdb0) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: _dl_fini () at dl-fini.c:231 __run_exit_handlers (status=0, listp=0x7f42f61945d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83 __GI_exit (status=) at exit.c:105 () () at /lib/x86_64-linux-gnu/libc.so.6 Title: lightdm crashed with SIGSEGV in _dl_fini() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1700391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783591] Re: lxc-user-nic allows unprivileged users to open arbitrary files
Upstream communication: https://lists.linuxcontainers.org/pipermail/lxc-
devel/2018-August/018336.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1783591
Title:
lxc-user-nic allows unprivileged users to open arbitrary files
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Bug description:
Matthias Gerstner from SUSE reported the following:
```
Hello,
following the lxc security reporting guidelines [1] I am reporting a
finding in the lxc-user-nic setuid binary. I'm encrypting this mail as a
best practice and because I found valid GPG keys for all of your
adresses. Please find my public key attached to this mail.
In the context of an openSUSE security audit of the lxc-user-nic setuid
binary [2] (currently private bug) I came across an issue that should be
adressed. In the "delete" case the program runs the following piece of
code unconditionally with effective uid 0 (from lxc_user_nic.c):
```
} else if (request == LXC_USERNIC_DELETE) {
netns_fd = open(args.pid, O_RDONLY);
if (netns_fd < 0) {
usernic_error("Could not open \"%s\": %s\n", args.pid,
strerror(errno));
exit(EXIT_FAILURE);
}
}
```
`args.pid` is a user controlled parameter and can be an arbitrary path
at the moment. Nothing is done with this file descriptor later on in the
program except an attempt at `setns(fd, CLONE_NEWNET)` in
`is_privileged_over_netns()`. Still this allows the unprivileged caller
of the setuid binary to achieve the following:
- it can test for existence of files normally not accessible to the
caller (information leak). Example:
```
# this file is existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.bash_history type
bridge nic
lxc_user_nic.c: 1017: is_privileged_over_netns: Failed to setns() to
network namespace Invalid argument
lxc_user_nic.c: 1161: main: Process is not privileged over network namespace
# this file is not existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.zsh_history type bridge
nic
lxc_user_nic.c: 1130: main: Could not open "/root/.zsh_history": No such
file or directory
```
- it allows to trigger code paths in the kernel that are normally not
accessible to the caller. This can happen when opening special files
like character and block devices or files in /proc or /sys. Opening
some of these files can cause lock or alloc operations or even more
complex things to happen like when opening /dev/ptmx, which causes the
allocation of a new master/slave pseudo terminal. Therefore this can
lead to DoS like situations or have further unspecified impact.
For fixing this I suggest opening the file supplied in `args.pid` only
with the permissions of the real user, since this is already done in
`is_privileged_over_netns()` anyway. Another approach would be the
normalization of the input path and then only allowing a path of the
pattern /proc//ns/net.
[1] https://github.com/lxc/lxc/blob/master/README.md#reporting-security-issues
[2] https://bugzilla.suse.com/show_bug.cgi?id=988348
Best regards
Matthias
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783591] Re: lxc-user-nic allows unprivileged users to open arbitrary files
All supported upstream branches have been updated with the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1783591
Title:
lxc-user-nic allows unprivileged users to open arbitrary files
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Bug description:
Matthias Gerstner from SUSE reported the following:
```
Hello,
following the lxc security reporting guidelines [1] I am reporting a
finding in the lxc-user-nic setuid binary. I'm encrypting this mail as a
best practice and because I found valid GPG keys for all of your
adresses. Please find my public key attached to this mail.
In the context of an openSUSE security audit of the lxc-user-nic setuid
binary [2] (currently private bug) I came across an issue that should be
adressed. In the "delete" case the program runs the following piece of
code unconditionally with effective uid 0 (from lxc_user_nic.c):
```
} else if (request == LXC_USERNIC_DELETE) {
netns_fd = open(args.pid, O_RDONLY);
if (netns_fd < 0) {
usernic_error("Could not open \"%s\": %s\n", args.pid,
strerror(errno));
exit(EXIT_FAILURE);
}
}
```
`args.pid` is a user controlled parameter and can be an arbitrary path
at the moment. Nothing is done with this file descriptor later on in the
program except an attempt at `setns(fd, CLONE_NEWNET)` in
`is_privileged_over_netns()`. Still this allows the unprivileged caller
of the setuid binary to achieve the following:
- it can test for existence of files normally not accessible to the
caller (information leak). Example:
```
# this file is existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.bash_history type
bridge nic
lxc_user_nic.c: 1017: is_privileged_over_netns: Failed to setns() to
network namespace Invalid argument
lxc_user_nic.c: 1161: main: Process is not privileged over network namespace
# this file is not existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.zsh_history type bridge
nic
lxc_user_nic.c: 1130: main: Could not open "/root/.zsh_history": No such
file or directory
```
- it allows to trigger code paths in the kernel that are normally not
accessible to the caller. This can happen when opening special files
like character and block devices or files in /proc or /sys. Opening
some of these files can cause lock or alloc operations or even more
complex things to happen like when opening /dev/ptmx, which causes the
allocation of a new master/slave pseudo terminal. Therefore this can
lead to DoS like situations or have further unspecified impact.
For fixing this I suggest opening the file supplied in `args.pid` only
with the permissions of the real user, since this is already done in
`is_privileged_over_netns()` anyway. Another approach would be the
normalization of the input path and then only allowing a path of the
pattern /proc//ns/net.
[1] https://github.com/lxc/lxc/blob/master/README.md#reporting-security-issues
[2] https://bugzilla.suse.com/show_bug.cgi?id=988348
Best regards
Matthias
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section
Thank you for looking into it, I used Ubuntu 18.04, the latest released. On Aug 7, 2018 12:21 AM, "Joshua Powers" wrote: Hi! Thanks for taking the time to file a bug. I have re-assigned this to network-manager as this isn't a bug with the vlan package, but with the UI itself. It may need to be moved to yet another package, but this should get the right people's attention. Could you also let us know what version of Ubuntu you are using? (e.g. `cat /etc/os-release`) Thanks! ** Package changed: vlan (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in network-manager package in Ubuntu: New Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1785311/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in network-manager package in Ubuntu: New Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1785311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783591] Re: lxc-user-nic allows unprivileged users to open arbitrary files
New version to apply cleanly to master.
** Patch added:
"0001-CVE-2018-6556-verify-netns-fd-in-lxc-user-nic-master.patch"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/+attachment/5172186/+files/0001-CVE-2018-6556-verify-netns-fd-in-lxc-user-nic-master.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1783591
Title:
lxc-user-nic allows unprivileged users to open arbitrary files
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Bug description:
Matthias Gerstner from SUSE reported the following:
```
Hello,
following the lxc security reporting guidelines [1] I am reporting a
finding in the lxc-user-nic setuid binary. I'm encrypting this mail as a
best practice and because I found valid GPG keys for all of your
adresses. Please find my public key attached to this mail.
In the context of an openSUSE security audit of the lxc-user-nic setuid
binary [2] (currently private bug) I came across an issue that should be
adressed. In the "delete" case the program runs the following piece of
code unconditionally with effective uid 0 (from lxc_user_nic.c):
```
} else if (request == LXC_USERNIC_DELETE) {
netns_fd = open(args.pid, O_RDONLY);
if (netns_fd < 0) {
usernic_error("Could not open \"%s\": %s\n", args.pid,
strerror(errno));
exit(EXIT_FAILURE);
}
}
```
`args.pid` is a user controlled parameter and can be an arbitrary path
at the moment. Nothing is done with this file descriptor later on in the
program except an attempt at `setns(fd, CLONE_NEWNET)` in
`is_privileged_over_netns()`. Still this allows the unprivileged caller
of the setuid binary to achieve the following:
- it can test for existence of files normally not accessible to the
caller (information leak). Example:
```
# this file is existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.bash_history type
bridge nic
lxc_user_nic.c: 1017: is_privileged_over_netns: Failed to setns() to
network namespace Invalid argument
lxc_user_nic.c: 1161: main: Process is not privileged over network namespace
# this file is not existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.zsh_history type bridge
nic
lxc_user_nic.c: 1130: main: Could not open "/root/.zsh_history": No such
file or directory
```
- it allows to trigger code paths in the kernel that are normally not
accessible to the caller. This can happen when opening special files
like character and block devices or files in /proc or /sys. Opening
some of these files can cause lock or alloc operations or even more
complex things to happen like when opening /dev/ptmx, which causes the
allocation of a new master/slave pseudo terminal. Therefore this can
lead to DoS like situations or have further unspecified impact.
For fixing this I suggest opening the file supplied in `args.pid` only
with the permissions of the real user, since this is already done in
`is_privileged_over_netns()` anyway. Another approach would be the
normalization of the input path and then only allowing a path of the
pattern /proc//ns/net.
[1] https://github.com/lxc/lxc/blob/master/README.md#reporting-security-issues
[2] https://bugzilla.suse.com/show_bug.cgi?id=988348
Best regards
Matthias
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785311] [NEW] VLAN in GUI's network setting is under Bluetooth section
You have been subscribed to a public bug: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- VLAN in GUI's network setting is under Bluetooth section https://bugs.launchpad.net/bugs/1785311 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section
Hi! Thanks for taking the time to file a bug. I have re-assigned this to network-manager as this isn't a bug with the vlan package, but with the UI itself. It may need to be moved to yet another package, but this should get the right people's attention. Could you also let us know what version of Ubuntu you are using? (e.g. `cat /etc/os-release`) Thanks! ** Package changed: vlan (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in network-manager package in Ubuntu: New Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1785311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783591] Re: lxc-user-nic allows unprivileged users to open arbitrary files
Also released to xenial-backports.
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1783591
Title:
lxc-user-nic allows unprivileged users to open arbitrary files
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Bug description:
Matthias Gerstner from SUSE reported the following:
```
Hello,
following the lxc security reporting guidelines [1] I am reporting a
finding in the lxc-user-nic setuid binary. I'm encrypting this mail as a
best practice and because I found valid GPG keys for all of your
adresses. Please find my public key attached to this mail.
In the context of an openSUSE security audit of the lxc-user-nic setuid
binary [2] (currently private bug) I came across an issue that should be
adressed. In the "delete" case the program runs the following piece of
code unconditionally with effective uid 0 (from lxc_user_nic.c):
```
} else if (request == LXC_USERNIC_DELETE) {
netns_fd = open(args.pid, O_RDONLY);
if (netns_fd < 0) {
usernic_error("Could not open \"%s\": %s\n", args.pid,
strerror(errno));
exit(EXIT_FAILURE);
}
}
```
`args.pid` is a user controlled parameter and can be an arbitrary path
at the moment. Nothing is done with this file descriptor later on in the
program except an attempt at `setns(fd, CLONE_NEWNET)` in
`is_privileged_over_netns()`. Still this allows the unprivileged caller
of the setuid binary to achieve the following:
- it can test for existence of files normally not accessible to the
caller (information leak). Example:
```
# this file is existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.bash_history type
bridge nic
lxc_user_nic.c: 1017: is_privileged_over_netns: Failed to setns() to
network namespace Invalid argument
lxc_user_nic.c: 1161: main: Process is not privileged over network namespace
# this file is not existing
$ /usr/lib/lxc/lxc-user-nic delete path name /root/.zsh_history type bridge
nic
lxc_user_nic.c: 1130: main: Could not open "/root/.zsh_history": No such
file or directory
```
- it allows to trigger code paths in the kernel that are normally not
accessible to the caller. This can happen when opening special files
like character and block devices or files in /proc or /sys. Opening
some of these files can cause lock or alloc operations or even more
complex things to happen like when opening /dev/ptmx, which causes the
allocation of a new master/slave pseudo terminal. Therefore this can
lead to DoS like situations or have further unspecified impact.
For fixing this I suggest opening the file supplied in `args.pid` only
with the permissions of the real user, since this is already done in
`is_privileged_over_netns()` anyway. Another approach would be the
normalization of the input path and then only allowing a path of the
pattern /proc//ns/net.
[1] https://github.com/lxc/lxc/blob/master/README.md#reporting-security-issues
[2] https://bugzilla.suse.com/show_bug.cgi?id=988348
Best regards
Matthias
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
Based on in-depth analysis, I found the cause of the error： “Apr 03 12:59:15 ubuntu systemd[1]: Failed to set up mount unit: Device or resource busy” call tree on systemd mount.c & unit.c: mount_dispatch_io -> mount_load_proc_self_mountinfo -> mount_setup_unit -> mount_setup_existing_unit -> mount_add_extras -> unit_set_default_slice: -> unit_set_slice: if (unit_active_state(u) != UNIT_INACTIVE) return -EBUSY; "unit_set_slice" return EBUSY always, because of nfsroot always active state in netbooting, "mount_dispatch_io" give up updating mount state when "mount_load_proc_self_mountinfo" return the error. finally, all systemd mount service failed and then goto emergency shell. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766566] Re: lib64z1: call dh_makeshlibs for the lib64z1 package
This bug was fixed in the package zlib - 1:1.2.8.dfsg-1ubuntu1.1 --- zlib (1:1.2.8.dfsg-1ubuntu1.1) trusty-proposed; urgency=medium * SRU: LP: #1766566. * Call dh_makeshlibs for the 64bit multilib package. -- Matthias Klose Tue, 24 Apr 2018 13:42:30 +0200 ** Changed in: zlib (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1766566 Title: lib64z1: call dh_makeshlibs for the lib64z1 package Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Trusty: Fix Released Bug description: SRU: dh_makeshlibs is not called for the lib64z1 package, letting packages which have dependencies on this library fail to build: DIRNAME=64 dh_shlibdeps -plib64gphobos71 -l/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64:/<>/debian/tmp/usr/lib64:/<>/debian/tmp/usr/x86_64-linux-gnu/lib -- -Ldebian/shlibs.common64 dpkg-shlibdeps: error: no dependency information found for /usr/lib64/libz.so.1 (used by debian/lib64gphobos71/usr/lib6 4/libgphobos.so.71.0.2) dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos71.substvars -l/lib/x86_64-linux-gnu -l/usr/lib/x86_64-linux-gnu -l/l ib64 -l/usr/lib64 -l/<>/debian/tmp/usr/lib64 -l/<>/debian/tmp/usr/x86_64-linux-gnu/lib -Ldebi an/shlibs.common64 debian/lib64gphobos71/usr/lib64/libgphobos.so.71.0.2 debian/lib64gphobos71/usr/lib64/libgdruntime.so .71.0.2 returned exit code 2 make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2 The fix is simple, and in wily and newer Ubuntu versions. SRU validation: the package builds, and dh_shlibdeps doesn't fail anymore for depending packages (e.g. the gcc-7 build in the ubuntu- toolchain-r/test directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1766566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766566] Update Released
The verification of the Stable Release Update for zlib has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1766566 Title: lib64z1: call dh_makeshlibs for the lib64z1 package Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Trusty: Fix Committed Bug description: SRU: dh_makeshlibs is not called for the lib64z1 package, letting packages which have dependencies on this library fail to build: DIRNAME=64 dh_shlibdeps -plib64gphobos71 -l/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64:/<>/debian/tmp/usr/lib64:/<>/debian/tmp/usr/x86_64-linux-gnu/lib -- -Ldebian/shlibs.common64 dpkg-shlibdeps: error: no dependency information found for /usr/lib64/libz.so.1 (used by debian/lib64gphobos71/usr/lib6 4/libgphobos.so.71.0.2) dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos71.substvars -l/lib/x86_64-linux-gnu -l/usr/lib/x86_64-linux-gnu -l/l ib64 -l/usr/lib64 -l/<>/debian/tmp/usr/lib64 -l/<>/debian/tmp/usr/x86_64-linux-gnu/lib -Ldebi an/shlibs.common64 debian/lib64gphobos71/usr/lib64/libgphobos.so.71.0.2 debian/lib64gphobos71/usr/lib64/libgdruntime.so .71.0.2 returned exit code 2 make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2 The fix is simple, and in wily and newer Ubuntu versions. SRU validation: the package builds, and dh_shlibdeps doesn't fail anymore for depending packages (e.g. the gcc-7 build in the ubuntu- toolchain-r/test directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1766566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766566] Re: lib64z1: call dh_makeshlibs for the lib64z1 package
Confirmed that the autopkgtest failures are not regressions caused by this upload. Releasing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1766566 Title: lib64z1: call dh_makeshlibs for the lib64z1 package Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Trusty: Fix Committed Bug description: SRU: dh_makeshlibs is not called for the lib64z1 package, letting packages which have dependencies on this library fail to build: DIRNAME=64 dh_shlibdeps -plib64gphobos71 -l/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64:/<>/debian/tmp/usr/lib64:/<>/debian/tmp/usr/x86_64-linux-gnu/lib -- -Ldebian/shlibs.common64 dpkg-shlibdeps: error: no dependency information found for /usr/lib64/libz.so.1 (used by debian/lib64gphobos71/usr/lib6 4/libgphobos.so.71.0.2) dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos71.substvars -l/lib/x86_64-linux-gnu -l/usr/lib/x86_64-linux-gnu -l/l ib64 -l/usr/lib64 -l/<>/debian/tmp/usr/lib64 -l/<>/debian/tmp/usr/x86_64-linux-gnu/lib -Ldebi an/shlibs.common64 debian/lib64gphobos71/usr/lib64/libgphobos.so.71.0.2 debian/lib64gphobos71/usr/lib64/libgdruntime.so .71.0.2 returned exit code 2 make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2 The fix is simple, and in wily and newer Ubuntu versions. SRU validation: the package builds, and dh_shlibdeps doesn't fail anymore for depending packages (e.g. the gcc-7 build in the ubuntu- toolchain-r/test directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1766566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785644] [NEW] Squared number (N^2) of copies printed
Public bug reported: I wanted to print 4 copies of a 3-pages document (12 pages total) and instead 16 copies (48 pages) were printed. Using latest Ubuntu with all updates, Gnome Shell on Xorg, I opened a PDF file in Evince 3.28.2-1, clicked "Print", clicked "+" button several times to increase the number of copies to 4, and sent it printing on Xerox_AltaLink_C8030. That network printer was previously auto-detected with default drivers. access_log only has one line at that time: localhost - - [06/Aug/2018:16:28:14 +0200] "POST /printers/Xerox_AltaLink_C8030 HTTP/1.1" 200 64269 Print-Job successful-ok error_log doesn’t have anything related. I am attaching the print job captured per https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data On the cups page with completed jobs http://localhost:631/printers/Xerox_AltaLink_C8030?which_jobs=completed the amount of pages is shown as "48". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:12:58 2018 InstallationDate: Installed on 2018-05-02 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Lexmark_M3150_10_: ipp://ET0021B7C1D744.local:631/ipp/print device for WorkCentre-7120: socket://10.2.20.114 device for Xerox_AltaLink_C8030: ipp://XRX9C934E98F100.local:631/ipp/print device for Xerox_VersaLink_C505_8c_ab_2c_4_: ipps://XC8cab2c.local:631/ipp/print device for Xerox_VersaLink_C505_8c_ab_50_7_: ipps://XC8cab50.local:631/ipp/print MachineType: Dell Inc. OptiPlex 7020 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd', '/etc/cups/ppd/Xerox_AltaLink_C8030.ppd', '/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd', '/etc/cups/ppd/WorkCentre-7120.ppd', '/etc/cups/ppd/Lexmark_M3150_10_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd: Permission denied Xerox_AltaLink_C8030: AltaLink C8030 grep: /etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd: Permission denied grep: /etc/cups/ppd/WorkCentre-7120.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_M3150_10_.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=3fd92192-fa04-40ea-ac71-f1dff8e153f7 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 02YYK5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd04/25/2014:svnDellInc.:pnOptiPlex7020:pvr01:rvnDellInc.:rn02YYK5:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic copies multiple print squared ** Attachment added: "Captured print job" https://bugs.launchpad.net/bugs/1785644/+attachment/5172144/+files/d00015-001 ** Description changed: I wanted to print 4 copies of a 3-pages document (12 pages total) and instead 16 copies (48 pages) were printed. Using latest Ubuntu with all updates, Gnome Shell on Xorg, I opened a PDF file in Evince 3.28.2-1, clicked "Print", clicked "+" button several times to increase the number of copies to 4, and sent it printing on Xerox_AltaLink_C8030. That network printer was previously auto-detected with default drivers. - access_log only has one line at that time: + access_log only has one line at that time: localhost - - [06/Aug/2018:16:28:14 +0200] "POST /printers/Xerox_AltaLink_C8030 HTTP/1.1" 200 64269 Print-Job successful-ok error_log doesn’t have anything related. I am attaching the print job captured per https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data + + On the cups page with completed jobs + http://localhost:631/printers/Xerox_AltaLink_C8030?which_jobs=completed + the amount of pages is shown as "48". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:12:58 2018 InstallationDate: Installed on 2018-05-02 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: - device for Lexmark_M3150_10_: ipp://ET0021B7C1D744.local:631/ipp/print - device for WorkCentre-7120:
[Touch-packages] [Bug 1734423] Re: package libdb5.3:amd64 5.3.28-11ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
i experienced the same issue at the start up of my pc :/ i dont know what to do :D i know that im hopeless >.< ** Changed in: db5.3 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/db5.3/+question/671392 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1734423 Title: package libdb5.3:amd64 5.3.28-11ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in db5.3 package in Ubuntu: Invalid Bug description: just started my laptop and this notification popped up, not sure if anything is broken. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdb5.3:amd64 5.3.28-11ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Nov 24 23:07:55 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgTerminalLog: dpkg: error processing package libdb5.3:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-10-18 (38 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: db5.3 Title: package libdb5.3:amd64 5.3.28-11ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1734423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
This bug was fixed in the package nux - 4.0.8+18.04.20180622.2-0ubuntu1 --- nux (4.0.8+18.04.20180622.2-0ubuntu1) bionic; urgency=medium * debian/control: update Vcs * debian/nux-tools.preinst: - Restore backup config files before installing nux-tools, so that they will be updaded with the fixed versions (LP: #1768610) * debian/rules: - build tests using LIBGL_ALWAYS_SOFTWARE env var to fix build crash on launchpad builders (there are memory errors in the hw drivers). -- Marco Trevisan (Treviño) Fri, 22 Jun 2018 13:05:07 + ** Changed in: xorg (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Released Status in xorg source package in Xenial: Fix Released Status in nux source package in Artful: Won't Fix Status in xorg source package in Artful: Won't Fix Status in nux source package in Bionic: Fix Released Status in xorg source package in Bionic: Fix Released Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED UNITY ] · remove nux-tools from artful/bionic-release (pre-sru), upgrade, reinstall nux-tools (no prompt) · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall nux-tools (nothing should be prompted) · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) · install nux-tools, upgrade, no prompt You end up with either no /etc/X11/Xsession.d/50_check_unity_support, its new contents or you are asked what to do if you've changed it before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
This bug was fixed in the package nux - 4.0.8+16.04.20180622.2-0ubuntu1 --- nux (4.0.8+16.04.20180622.2-0ubuntu1) xenial; urgency=medium * debian/control: update Vcs * debian/nux-tools.preinst: - Restore backup config files before installing nux-tools, so that they will be updaded with the fixed versions (LP: #1768610) -- Marco Trevisan (Treviño) Fri, 22 Jun 2018 13:16:40 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Released Status in xorg source package in Xenial: Fix Released Status in nux source package in Artful: Won't Fix Status in xorg source package in Artful: Won't Fix Status in nux source package in Bionic: Fix Released Status in xorg source package in Bionic: Fix Released Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED UNITY ] · remove nux-tools from artful/bionic-release (pre-sru), upgrade, reinstall nux-tools (no prompt) · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall nux-tools (nothing should be prompted) · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) · install nux-tools, upgrade, no prompt You end up with either no /etc/X11/Xsession.d/50_check_unity_support, its new contents or you are asked what to do if you've changed it before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
This bug was fixed in the package xorg - 1:7.7+19ubuntu7.1 --- xorg (1:7.7+19ubuntu7.1) bionic; urgency=medium * x11-common.preinst: - Rename nux config leftovers which might change the environment even when not running an unity session (LP: #1768610) * debian/control: - x11-common breaks nux-tools (<< 4.0.8+18.04.20180613.5-0ubuntu1) - this version contains the fixed conffile; if it's installed on the system we need people to be upgraded to the new version. -- Marco Trevisan (Treviño) Thu, 21 Jun 2018 11:48:13 +0100 ** Changed in: xorg (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Released Status in xorg source package in Xenial: Fix Released Status in nux source package in Artful: Won't Fix Status in xorg source package in Artful: Won't Fix Status in nux source package in Bionic: Fix Released Status in xorg source package in Bionic: Fix Released Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED UNITY ] · remove nux-tools from artful/bionic-release (pre-sru), upgrade, reinstall nux-tools (no prompt) · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall nux-tools (nothing should be prompted) · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) · install nux-tools, upgrade, no prompt You end up with either no /etc/X11/Xsession.d/50_check_unity_support, its new contents or you are asked what to do if you've changed it before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
This bug was fixed in the package xorg - 1:7.7+13ubuntu3.1 --- xorg (1:7.7+13ubuntu3.1) xenial; urgency=medium * x11-common.preinst: - Rename nux config leftovers which might change the environment even when not running an unity session (LP: #1768610) * debian/control: - x11-common breaks nux-tools (<< 4.0.8+16.04.20180613.1-0ubuntu1) - this version contains the fixed conffile; if it's installed on the system we need people to be upgraded to the new version. -- Marco Trevisan (Treviño) Thu, 21 Jun 2018 12:04:37 +0100 ** Changed in: nux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Released Status in xorg source package in Xenial: Fix Released Status in nux source package in Artful: Won't Fix Status in xorg source package in Artful: Won't Fix Status in nux source package in Bionic: Fix Released Status in xorg source package in Bionic: Fix Released Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED UNITY ] · remove nux-tools from artful/bionic-release (pre-sru), upgrade, reinstall nux-tools (no prompt) · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall nux-tools (nothing should be prompted) · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) · install nux-tools, upgrade, no prompt You end up with either no /etc/X11/Xsession.d/50_check_unity_support, its new contents or you are asked what to do if you've changed it before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 778919] Re: package vim-common 2:7.2.330-1ubuntu4 failed to install/upgrade: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2
Steve, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to that which you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/778919 Title: package vim-common 2:7.2.330-1ubuntu4 failed to install/upgrade: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2.8-0ubuntu3 Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim Hello, There seems to be a conflict between vim-common and llvm-dev on file /usr/share/vim/vimcurrent. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: vim-common 2:7.2.330-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 Architecture: i386 Date: Fri May 6 23:54:21 2011 ErrorMessage: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2.8-0ubuntu3 SourcePackage: vim Title: package vim-common 2:7.2.330-1ubuntu4 failed to install/upgrade: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2.8-0ubuntu3 UpgradeStatus: Upgraded to natty on 2011-05-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/778919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 401790] Re: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序·post-installation script·返回了錯誤號·2
ywc9393, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to that which you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/401790 Title: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序 ·post-installation script·返回了錯誤號·2 Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序 ·post-installation script·返回了錯誤號·2 ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: 子程序·post-installation script·返回了錯誤號·2 Package: vim-gnome 2:7.2.079-1ubuntu5 SourcePackage: vim Title: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序·post-installation script·返回了錯誤號·2 Uname: Linux 2.6.28-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/401790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 298530] Re: gvim occasionally crashes when file changed outside it
Ken, Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates. It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal: apport-collect 298530 and add any additional information that you think relevant. Alternatively, please confirm that this is no longer a problem and that we can close the report. If we do not hear from you the bug report will close itself in approximately two months time. Thank you again for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/298530 Title: gvim occasionally crashes when file changed outside it Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim I am using gvim to read a file created by a program. gvim will irregularly crash when the file is changed underneath it and you click 'Load' in the dialogue box. It come up with a invalid nline. Seems to be when the file is shortened from the original, have not determined a pattern yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/298530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319881] Re: package vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.
Henry, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to that which you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1319881 Title: package vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim- runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz] failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: This was part of a do-upgrade from saucy to trusty ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz] ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 Date: Thu May 15 15:53:10 2014 DuplicateSignature: package:vim-runtime:2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz]:ErrorMessage: subprocess new pre-installation script returned error exit status 2 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 2 InstallationDate: Installed on 2013-01-05 (494 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) PackageArchitecture: all SourcePackage: vim Title: package vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz] failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2014-05-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1319881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 694299] Re: The Gvim's menu is not normal, except for "Help"
Cloudy, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/694299 Title: The Gvim's menu is not normal,except for "Help" Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim Today I want to try the Gvim, when I open it ,its menu is not display, but if I click it, it will display ,and also can't full display. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-gnome 2:7.2.330-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Sat Dec 25 23:43:24 2010 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=zh_CN.utf8 SHELL=/bin/bash SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/694299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 896725] Re: package vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] failed to install/upgrade: ErrorMessage:
Rock, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/896725 Title: package vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] failed to install/upgrade: ErrorMessage: subprocess installed post- installation script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: Happened during upgrade to Ubuntu 11.10. ProblemType: Package DistroRelease: Ubuntu 11.10 Package: vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 26 17:58:25 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: vim Title: package vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to oneiric on 2011-11-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/896725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1174556] Re: package vim-tiny 2:7.3.547-6ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Rosario, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1174556 Title: package vim-tiny 2:7.3.547-6ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: this happens every time I try to install a new package or when I try to upgrade ubuntu, please help ProblemType: Package DistroRelease: Ubuntu 13.04 Package: vim-tiny 2:7.3.547-6ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Apr 29 23:46:03 2013 DuplicateSignature: Setting up vim-tiny (2:7.3.547-6ubuntu5) ... update-alternatives: error: /var/lib/dpkg/alternatives/rview corrupt: invalid status dpkg: error processing vim-tiny (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2012-04-16 (378 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True SourcePackage: vim Title: package vim-tiny 2:7.3.547-6ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1174556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1077788] Re: package vim-gnome 2:7.3.547-4ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Lutf, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1077788 Title: package vim-gnome 2:7.3.547-4ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: Every time I log on after a few minutes. I get the error message. Most of the time I ignore it but I want to fix this. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: vim-gnome 2:7.3.547-4ubuntu1.1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 9 14:18:53 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 2 MarkForUpload: True SourcePackage: vim Title: package vim-gnome 2:7.3.547-4ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1077788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1280766] Re: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
William, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1280766 Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: Ubuntu 12.4 arm trying to install/purge/remove vim returns errors each time. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: vim 2:7.3.429-2ubuntu2.1 Uname: Linux 3.0.35-gbe699c6-dirty armv7l ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: vim: Purge Architecture: armel Date: Sun Feb 16 12:44:05 2014 DpkgTerminalLog: Removing vim ... update-alternatives: error: /var/lib/dpkg/alternatives/rvim corrupt: line not terminated while trying to read status dpkg: error processing vim (--purge): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:vim:2:7.3.429-2ubuntu2.1:subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 MarkForUpload: True SourcePackage: vim Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2014-02-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1280766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 407259] Re: Cannot uninstall vim-gnome
Ttoft, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/407259 Title: Cannot uninstall vim-gnome Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim-gnome Tried to uninstall the package but something went wrong it seems. ProblemType: Package Architecture: amd64 DistroRelease: Ubuntu 9.04 ErrorMessage: underproces pre-removal script returnerede afslutningsstatus 2 NonfreeKernelModules: fglrx Package: vim-gnome 2:7.2.079-1ubuntu5 SourcePackage: vim Title: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: underproces pre-removal script returnerede afslutningsstatus 2 Uname: Linux 2.6.28-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/407259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 885535] Re: package vim 2:7.3.035 hg~8fdc12103333-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Rock, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Can this bug report now be closed or do you still see a problem related to what you reported? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/885535 Title: package vim 2:7.3.035 hg~8fdc1210-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Incomplete Bug description: i ran this command, sudo apt-get install vim-runtime. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: vim 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 AptOrdering: vim-runtime: Install vim: Install vim-runtime: Configure vim: Configure Architecture: amd64 Date: Wed Nov 2 22:44:00 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: vim Title: package vim 2:7.3.035+hg~8fdc1210-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/885535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785629] [NEW] [MIR] gupnp-av
Public bug reported: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu ** Affects: gupnp-av (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp-av in Ubuntu. https://bugs.launchpad.net/bugs/1785629 Title: [MIR] gupnp-av Status in gupnp-av package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785400] Re: Unable to locate package python3-defaults
Thanks. However, as I wrote in the original report packages such as python-venv also fail. I found a fix by adding “universe” to my sources.list. Hopefully that is the correct solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1785400 Title: Unable to locate package python3-defaults Status in python3-defaults package in Ubuntu: Invalid Bug description: Installed 18.04.1 Server AMD Trying to get pip3 and venv to work but I get the following: sudo apt install python3-defaults Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-defaults same thing for python3-pip3, python3-venv have done apt update already. sources.list has the following (untouched after installation of OS) deb http://archive.ubuntu.com/ubuntu bionic main deb http://archive.ubuntu.com/ubuntu bionic-security main deb http://archive.ubuntu.com/ubuntu bionic-updates main I can't find this package anywhere. What do I add to sources.list to fix this? Thanks for any help and apologies if the solution is obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1785400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS
** Package changed: colord (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1612708 Title: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS Status in gvfs package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.1 LTS colord: Installiert: 1.2.12-1ubuntu1 Installationskandidat: 1.2.12-1ubuntu1 Versionstabelle: *** 1.2.12-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb- share:server=nasdo,share=public' and I have created a Symbolic Link to this point with 'ln -s /run/user/1000/gvfs/smb- share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link folders, and files on the NAS have been accessable with r/w from Ubuntu 14.04 LTS. This is, what I expect from 16.04, too. Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the links seem to be the same, but opening a file does not work. It comes to an input/output error. I can use the links to folders to navigate, but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do I have access to mail folder via Thunderbird. Using gvfs-mount creates a shared folder in Nautilus called public. Using this way to access the NAS, and open the Calc file works with ubuntu 16.04 LTS fine. Locking to the syslog while trying to open a file creates the following entries: Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service. Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Der angegebene Ort ist nicht eingehängt Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Der angegebene Ort ist nicht eingehängt Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler. Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler. Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler. Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service... Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 'org.freedesktop.hostname1' Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1612708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 1710637 *** https://bugs.launchpad.net/bugs/1710637 Fixed for me by executing kbd_mode -s. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID
The patch "resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN- with.patch" for bug #1727237 seems to be the root cause of my problems (now reported separately in bug #1785383.) As the patch changes the transaction restart logic it may be worth the OP rebuilding without that patch and retesting. @xnox: my understanding is still that upstream recommendation is to use libnss-resolve, it is still there in the latest man pages. The handling of resolv.conf is to a certain extent orthogonal, as that file is only used by systemd to exchange nameserver info with "legacy" code.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771353 Title: Server feature level is now lower than when we began our transaction. Restarting with new ID Status in systemd package in Ubuntu: Confirmed Bug description: systemd 237-3ubuntu10 from bionic There is no /etc/netplan/* file. I'm getting some sort of a loop when systemd-resolved tries to resolve the hostname of my canonistack instance: ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed systemd-resolved debug output loops over like this: Transaction 36341 is now 19121. Cache miss for bip.lcy02.canonistack IN A Transaction 19121 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 19121. Sending query packet with id 19121. Processing incoming packet on transaction 19121. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. Transaction 19121 is now 17157. Cache miss for bip.lcy02.canonistack IN A Transaction 17157 for scope dns on */*. Using feature level UDP+EDNS0 for transaction 17157. Sending query packet with id 17157. Processing incoming packet on transaction 17157. (rcode=SUCCESS) Server feature level is now lower than when we began our transaction. Restarting with new ID. ... Packet capture shows a loop like this: 13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55) 13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50) 13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55) I'm going to attach the full debug output, and the pcap file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726929] Re: pulseaudio crashed with SIGABRT in __GI_____strtof128_l_internal()
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726929 Title: pulseaudio crashed with SIGABRT in __GI_strtof128_l_internal() Status in pulseaudio package in Ubuntu: Incomplete Bug description: In sound panel, the analog output keeps appearing/disappearing for a minute or so. Then this crash occurs. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: henklaak F...m firefox /dev/snd/controlC0: henklaak F firefox henklaak 6370 F alsamixer /dev/snd/timer: henklaak f firefox CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Tue Oct 24 18:07:04 2017 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-04-25 (547 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-switch-on-port-available.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690026] Re: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_inf
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690026 Title: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_info() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/09eaa7a762edd70e8a3d904cb32f366b3c3211a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690071] Re: pulseaudio crashed with SIGABRT in resampler_basic_interpolate_single() from speex_resampler_process_native() from speex_resampler_process_float() from speex_resampl
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690071 Title: pulseaudio crashed with SIGABRT in resampler_basic_interpolate_single() from speex_resampler_process_native() from speex_resampler_process_float() from speex_resampler_process_interleaved_float() from speex_resample_float() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/aae62bd41aea287ef4e95b261916bd17e9f6788f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690058] Re: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from fit_buf() from convert_from_work_format() from pa_resampler_run()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690058 Title: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from fit_buf() from convert_from_work_format() from pa_resampler_run() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/aeb8690531ca05af2487bc3f5f6552bdb5fff7d8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690029] Re: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from fit_buf() from convert_to_work_format() from pa_resampler_run()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690029 Title: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from fit_buf() from convert_to_work_format() from pa_resampler_run() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/8ee8dc06021eb07d5f02c2823ca91f441b5b1ae7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690050] Re: pulseaudio crashed with SIGABRT in pa_rtpoll_set_timer_relative() from thread_func() from internal_thread_func() from start_thread() from clone()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690050 Title: pulseaudio crashed with SIGABRT in pa_rtpoll_set_timer_relative() from thread_func() from internal_thread_func() from start_thread() from clone() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7b48f61206e9d4d82be7ff893f162e20c5c4538b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690064] Re: pulseaudio crashed with SIGABRT in pa_memblock_unref() from drop_block() from drop_backlog() from pa_memblockq_drop() from pa_sink_input_drop()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690064 Title: pulseaudio crashed with SIGABRT in pa_memblock_unref() from drop_block() from drop_backlog() from pa_memblockq_drop() from pa_sink_input_drop() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/114999a1ffc982bfc5fb50105a1ca8f4cfe5ab4a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726074] Re: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() from pa_memblockq_push_align()
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726074 Title: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() from pa_memblockq_push_align() Status in pulseaudio package in Ubuntu: Incomplete Bug description: No action by user - listening to Pandora in Chromium while working in LibreOffice. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 10674 F pulseaudio /dev/snd/pcmC1D0p: mike 10674 F...m pulseaudio /dev/snd/controlC1: mike 10674 F pulseaudio CurrentDesktop: KDE Date: Sun Oct 22 12:56:26 2017 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: pa_mcalign_csize () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so pa_memblockq_push_align () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so pa_sink_input_peek () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_sink_render_into () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so Title: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo dmi.bios.date: 04/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632515] Re: pulseaudio crashes with SIGABRT in do_read() from do_pstream_read_write() from dispatch_defer() from pa_mainloop_dispatch() pa_mainloop_iterate()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1632515 Title: pulseaudio crashes with SIGABRT in do_read() from do_pstream_read_write() from dispatch_defer() from pa_mainloop_dispatch() pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with version 1:8.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/ecdb0e073214b632d4edaaf7f99adc36b48f8583 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1632515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690045] Re: pulseaudio crashed with SIGABRT in pa_memblock_release() from pa_srbchannel_free() from check_srbpending() from check_srbpending() from pa_pstream_set_srbchannel()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690045 Title: pulseaudio crashed with SIGABRT in pa_memblock_release() from pa_srbchannel_free() from check_srbpending() from check_srbpending() from pa_pstream_set_srbchannel() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5fe9678dbacf2a09c15684b9139209f0be7ca572 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Changed in: hundredpapercuts Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1640139 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in One Hundred Papercuts: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial # uname -a Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux tried removing pulseaudio ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rotemfo2383 F pulseaudio /dev/snd/controlC0: rotemfo2383 F pulseaudio Date: Tue Nov 8 12:46:09 2016 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2016-10-25 (14 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1640139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690032] Re: pulseaudio crashed with SIGABRT in memcpy() from pa_srbchannel_write() from do_write() from do_pstream_read_write() from dispatch_defer()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690032 Title: pulseaudio crashed with SIGABRT in memcpy() from pa_srbchannel_write() from do_write() from do_pstream_read_write() from dispatch_defer() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/bb32c95da0ea7a15e0ddb2a30ad1e12b96d8bc06 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659980] Re: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from fit_buf:remap_channels() from pa_resampler_run()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1659980 Title: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from fit_buf:remap_channels() from pa_resampler_run() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:8.0-0ubuntu3.2, the problem page at https://errors.ubuntu.com/problem/dac9c12261f3350d6c910b91453999b8e8a69412 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1659980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690052] Re: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from en
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690052 Title: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_handler() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/49a8e58cea0b15b22d3a3cdbb1d736e619467e34 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712529] Re: pulseaudio crashed with SIGABRT in pa_source_output_attach()
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1712529 Title: pulseaudio crashed with SIGABRT in pa_source_output_attach() Status in pulseaudio package in Ubuntu: Incomplete Bug description: Just upgraded packages in 17.10 dev and rebooted and this crash popped out. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shemgp15659 F pulseaudio CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Aug 23 17:02:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2015-09-28 (694 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_source_output_attach () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_source_attach_within_thread () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-echo-cancel.so pa_source_process_msg () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/libalsa-util.so Title: pulseaudio crashed with SIGABRT in pa_source_output_attach() UpgradeStatus: Upgraded to artful on 2017-08-12 (10 days ago) UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video dmi.bios.date: 09/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GCETA3WW (2.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 34361A0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 34361A0 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1712529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: totem (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started Status in gst-plugins-good1.0 package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: artful desktop Test Case. 1. Pair a BT Speaker and set the output channel to the speaker 2. Play something with vlc or totem (and make sure it uses the speaker with pavucontrol for instance) 3. Switch the output to another channel eg internal speaker and turn the BT speaker off (do not close the music player) 4. Turn the speaker back on and wait until it connects 5. If the speaker is not selected automatically as the output, select it in the sound settings 6. Resume playing in VLC Expected result The track plays on the speaker Actual result It plays on the internal audio. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 17:09:17 2017 InstallationDate: Installed on 2013-09-03 (1412 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1704807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727867] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from _int_realloc() from __GI___libc_realloc() from g_realloc() from g_string_maybe_expand
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1727867 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from _int_realloc() from __GI___libc_realloc() from g_realloc() from g_string_maybe_expand() from g_string_append_vprintf() Status in bluez package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0 --- While trying to pair with a mouse (microsoft sculpt mouse) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 26 23:42:52 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2017-06-22 (125 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FBCTO1WW ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/vg--hostname-root--ubuntu ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f6907f6d108 : mov 0x8(%rbx),%rax PC (0x7f6907f6d108) ok source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: bluez StacktraceTop: malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489 _int_malloc (av=av@entry=0x7f69082bec20 , bytes=bytes@entry=1025) at malloc.c:3705 _int_realloc (av=av@entry=0x7f69082bec20 , oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at malloc.c:4626 __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245 g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: Upgraded to artful on 2017-10-09 (17 days ago) UserGroups: dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FBCTO1WW dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A4:71:4F:31:79 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:980135 acl:0 sco:0 events:12127 errors:0 TX bytes:605335 acl:0 sco:0 commands:2477 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1727867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366819] Re: pulseaudio crashed with SIGABRT in subscribe_callbac() from defer_cb() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1366819 Title: pulseaudio crashed with SIGABRT in subscribe_callbac() from defer_cb() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/50ffcb3cd067bebb38c6999f57504f533bc61800 --- PulseAudio crash error occurred without PulseAudio or any audio application open. Error occurred while opening new Firefox 32 tab. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Sep 8 08:42:12 2014 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-09-02 (6 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140826.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/16/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.60 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.60:bd01/16/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMKU-04002Q:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P50-A dmi.product.version: PSPMKU-04002Q dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1366819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689432] Re: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list"
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689432 Title: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list" Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a0e2acef0b29137ce41d624db0f08893d7ee9636 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1366418 Title: Bluetooth BCM43142A0 doesn’t work Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Incomplete Bug description: I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not displayed in the menu bar, if I open the bluetooth UI and switch on, nothing happens and the result of “hcitool dev” is empty. I have tried to install the windows driver with ndiswrapper, and the bluetooth device seems to be detected as an usb bluetooth device but still not working. I then add the device to the bluetooth usb device and was able to activate bluetooth in the UI but it does not detect any other devices (I’ve tested with a smartphone). The driver I have installed can be found in asus page => http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/ Select Windows OS, then “bluetooth” section, take the Broadcom driver (should be the first one). If you extract this archive, you will find a file named “bcbtums- win8x64-brcm.inf” which I installed using the following command: ndiswrapper -i bcbtums-win8x64-brcm.inf Then, the result of “ndiswrapper -l” is: bcbtums-win8x64-brcm : driver installed device (04CA:2006) present in usb-devices, I find a device which was not present before installation (I might have activated btusb before on this paste): T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=2006 Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM43142A0 S: SerialNumber=B8EE6593D989 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I can switch usb on, but no device will be detected and I’ve found this in the dmesg: [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout which looks pretty much like a “bluetooth not working” message which I don’t understand in details. I leave here my full dmesg: [0.253889] NetLabel: domain hash size = 128 [0.253890] NetLabel: protocols = UNLABELED CIPSOv4 [0.253901] NetLabel: unlabeled traffic allowed by default [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter [0.255995] Switched to clocksource hpet [0.260468] AppArmor: AppArmor Filesystem Enabled [0.260488] pnp: PnP ACPI init [0.260500] ACPI: bus type PNP registered [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) [0.260642] pnp 00:01: [dma 4] [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active) [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active) [0.260924] system 00:04: [io 0x0680-0x069f] has been reserved [0.260927] system 00:04: [io 0x] has been reserved [0.260928] system 00:04: [io 0x] has been reserved [0.260930] system 00:04: [io 0x] has been reserved [0.260932] system 00:04: [io 0x1c00-0x1cfe] has been reserved [0.260934] system 00:04: [io 0x1d00-0x1dfe] has been reserved [0.260935] system 00:04: [io 0x1e00-0x1efe] has been reserved [0.260937] system 00:04: [io 0x1f00-0x1ffe] has been reserved [0.260939] system 00:04: [io 0x1800-0x18fe] could not be reserved [0.260941] system 00:04: [io 0x164e-0x164f] has been reserved [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [0.260969] pnp 00:05: Plug and
[Touch-packages] [Bug 1689463] Re: bluetoothd crashing with SIGSEGV in ba2str from update_bredr_services from browse_cb from search_completed_cb from sdp_process
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689463 Title: bluetoothd crashing with SIGSEGV in ba2str from update_bredr_services from browse_cb from search_completed_cb from sdp_process Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/34f2d57d9e4087da25c8712bf1ea880ced7a88b6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689460] Re: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689460 Title: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b07fc39aa06a535581fad194d445c76f189364c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689438] Re: bluetoothd crashed with SIGABRT in free(): invalid pointer
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689438 Title: bluetoothd crashed with SIGABRT in free(): invalid pointer Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9690f8797e673b0fa8359647ae193ab8d0a62d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689442] Re: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689442 Title: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffbe12b82b8b2181e3dc736bea0a598f3b61042 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708774] Re: bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_reso
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1708774 Title: bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_resolved() Status in bluez package in Ubuntu: Incomplete Bug description: This is happening over and over while running behind the scenes. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: bluez 5.45-0ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Jul 31 22:44:35 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2017-07-29 (6 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: initrd=\ubuntu\initrd.img-generic root=/dev/mapper/volgrp-root rw SegvAnalysis: Segfault happened at: 0x7f2b54231cf0:mov(%rdi),%rax PC (0x7f2b54231cf0) ok source "(%rdi)" (0x3130383130303038) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: bluez StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () ?? () ?? () Title: bluetoothd crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F4:5C:89:C2:92:3C ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1054 acl:0 sco:0 events:59 errors:0 TX bytes:2965 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689435] Re: bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689435 Title: bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/257c18b3cbc69a5ebb4fc9e4efa0f5564822daf0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 --- Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690054] Re: pulseaudio crashed with SIGABRT in pa_sink_input_attach() from pa_sink_attach_within_thread() from pa_sink_process_msg() from sink_process_msg() from asyncmsgq_read_
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690054 Title: pulseaudio crashed with SIGABRT in pa_sink_input_attach() from pa_sink_attach_within_thread() from pa_sink_process_msg() from sink_process_msg() from asyncmsgq_read_work() Status in pulseaudio package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/cba7a3bcc7f260f8aab11c71680f8742fbbb03b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556324] Re: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1556324 Title: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 5.36-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/20c758a42f23b514e8bc98469a414de3ed9b727f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1556324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690040] Re: pulseaudio crashed with SIGABRT in pa_channel_map_init_extend() from pa_alsa_open_by_device_string() from pa_alsa_open_by_template() mapping_open_pcm() from pa_alsa_
Fix Released, apparently. Zero reports of this crash after 17.10. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690040 Title: pulseaudio crashed with SIGABRT in pa_channel_map_init_extend() from pa_alsa_open_by_device_string() from pa_alsa_open_by_template() mapping_open_pcm() from pa_alsa_profile_set_probe() Status in pulseaudio package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1f3a0ca523e35e21b988631ea8d15f6f3610cc7b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689443] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689443 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
