[Touch-packages] [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
No, unless you were afraid that what ticked open-vm-tools into having issues here being a wider more general issue. But then given that 16.04 is used widely for quite some time I think we can assume it is a corner case only. incomplete on the systemd task is ok. -- 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/1750780 Title: Race with local file systems can make open-vm-tools fail to start Status in cloud-init: Invalid Status in open-vm-tools package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in open-vm-tools source package in Xenial: Fix Released Status in systemd source package in Xenial: Incomplete Status in open-vm-tools source package in Artful: Fix Released Status in open-vm-tools package in Debian: Fix Released Bug description: Since the change in [1] open-vm-tools-service starts very (very) early. Not so much due to the Before=cloud-init-local.service But much more by DefaultDependencies=no That can trigger an issue that looks like root@ubuntuguest:~# systemctl status -l open-vm-tools.service ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor preset: enabled) Active: failed (Result: resources) As it is right now open-vm-tools can race with the other early start and then fail. In detail one can find a message like: open-vm-tools.service: Failed to run 'start' task: Read-only file system" This is due to privtaeTmp=yes which is also set needing a writable /var/tmp [2] To ensure this works PrivateTmp would have to be removed (not good) or some after dependencies added that make this work reliably. I added After=local-fs.target which made it work for me in 3/3 tests. I' like to have an ack by the cloud-init Team that this does not totally kill the originally intended Before=cloud-init-local.service I think it does not as local-fs can complete before cloud-init-local, then open-vm-tools can initialize and finally cloud-init-local can pick up the data. To summarize: # cloud-init-local # DefaultDependencies=no Wants=network-pre.target After=systemd-remount-fs.service Before=NetworkManager.service Before=network-pre.target Before=shutdown.target Before=sysinit.target Conflicts=shutdown.target RequiresMountsFor=/var/lib/cloud # open-vm-tools # DefaultDependencies=no Before=cloud-init-local.service Proposed is to add to the latter: After=local-fs.target [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677 [2]: https://github.com/systemd/systemd/issues/5610 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1796788] [NEW] resize2fs: Illegal indirect block found while trying to resize
Public bug reported: The new resize2fs(1.43+) failed to resize attached image file, and e2fsck didn't report any error before the resizing. Test steps: 1/ truncate -s 220M userdata.img 2/ e2fsck -fy userdata.img 3/ resize2fs userdata.img Result: When using resize2fs from e2fsprogs 1.43+(tested 1.43.4/1.43.5/1.44.4), it would abort with: Resizing the filesystem on userdata.img to 225280 (1k) blocks. resize2fs: Illegal indirect block found while trying to resize userdata.img Please run 'e2fsck -fy userdata.img' to fix the filesystem after the aborted resize operation. More information: 1/ The image is generated on xenial with genext2fs 2/ It works well on xenial with e2fsprogs 1.42.13-1ubuntu1 3/ It works well when resizing with a size less than 220M, for example "resize2fs userdata.img 219M" ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "test image" https://bugs.launchpad.net/bugs/1796788/+attachment/5198956/+files/userdata.img -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1796788 Title: resize2fs: Illegal indirect block found while trying to resize Status in e2fsprogs package in Ubuntu: New Bug description: The new resize2fs(1.43+) failed to resize attached image file, and e2fsck didn't report any error before the resizing. Test steps: 1/ truncate -s 220M userdata.img 2/ e2fsck -fy userdata.img 3/ resize2fs userdata.img Result: When using resize2fs from e2fsprogs 1.43+(tested 1.43.4/1.43.5/1.44.4), it would abort with: Resizing the filesystem on userdata.img to 225280 (1k) blocks. resize2fs: Illegal indirect block found while trying to resize userdata.img Please run 'e2fsck -fy userdata.img' to fix the filesystem after the aborted resize operation. More information: 1/ The image is generated on xenial with genext2fs 2/ It works well on xenial with e2fsprogs 1.42.13-1ubuntu1 3/ It works well when resizing with a size less than 220M, for example "resize2fs userdata.img 219M" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1796788/+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 776694] Re: Ubuntu 11.04 Network printer is inaccessible was ok in Ubuntu 10.10
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/776694 Title: Ubuntu 11.04 Network printer is inaccessible was ok in Ubuntu 10.10 Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups I can find network printer but won't verify states PRINT SHARE INACCESSIBLE and won't install. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Tue May 3 22:36:42 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer AOA110 Papersize: letter ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=25cfa824-c908-406e-a687-54f649878cf6 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3310 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA110:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: AOA110 dmi.product.version: 1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/776694/+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 485480] Re: cups converts multiple times between pdf and ps
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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: Expired 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 resume=UUID=628f8588-b1c4-47d2-af0d-2c83df012ff1 ProcEnviron: LANGUAGE=de_DE:de:en_GB:en PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.50-386 SourcePackage: cups Uname: Linux 2.6.31-15-386 i686
[Touch-packages] [Bug 768111] Re: remote printing: lpr: Connection refused
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/768111 Title: remote printing: lpr: Connection refused Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups This is what happens when trying to print to a remote server ~$ lpr -H servername -P queuename test.ps lpr: Connection refused Using lpr from lprng, remote printing to the same queues works $ lpr -Pqueuename@servername test.ps ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups-bsd 1.4.6-5ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Apr 21 09:22:44 2011 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Papersize: a4 ProcEnviron: LANGUAGE= LANG=C SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=/dev/mapper/vg0-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: TMIBX10H.86A.0043.2011.0322.1643 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ57TM dmi.board.vendor: Intel Corporation dmi.board.version: AAE70931-401 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0043.2011.0322.1643:bd03/22/2011:svntranstecAG:pn:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-401:cvn:ct3:cvr: dmi.sys.vendor: transtec AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/768111/+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 674246] Re: printers.conf integrity problems
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/674246 Title: printers.conf integrity problems Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups 1.4.3-1ubuntu1.3 On multiple occasions, I have witnessed a machine under heavy load experience a corrupted printers.conf file. In at least one instance, the file was partially truncated leading to the loss of approximately half of the printers. In another instance, printers.conf went missing entirely, leaving only printers.conf.O behind. An example log from the latter event is as follows... I [09/Nov/2010:10:06:38 +] Saving printers.conf... I [09/Nov/2010:10:06:38 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:06:38 +] Saving subscriptions.conf... I [09/Nov/2010:10:07:08 +] Saving printers.conf... I [09/Nov/2010:10:07:08 +] Saving subscriptions.conf... I [09/Nov/2010:10:07:38 +] Saving printers.conf... I [09/Nov/2010:10:07:38 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:07:38 +] Saving subscriptions.conf... I [09/Nov/2010:10:08:08 +] Saving printers.conf... I [09/Nov/2010:10:08:08 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:08:08 +] Saving subscriptions.conf... W [09/Nov/2010:10:08:20 +] Possible DoS attack - more than 10 clients connecting from ! I [09/Nov/2010:10:08:38 +] Saving printers.conf... I [09/Nov/2010:10:08:38 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:08:38 +] Saving subscriptions.conf... I [09/Nov/2010:10:09:08 +] Saving printers.conf... I [09/Nov/2010:10:09:08 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:09:08 +] Saving subscriptions.conf... W [09/Nov/2010:10:09:24 +] Possible DoS attack - more than 10 clients connecting from ! I [09/Nov/2010:10:09:39 +] Saving printers.conf... I [09/Nov/2010:10:09:39 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:09:39 +] Saving subscriptions.conf... E [09/Nov/2010:10:09:43 +] Unable to encrypt connection from - A TLS packet with unexpected length was received. I [09/Nov/2010:10:10:00 +] Scheduler shutting down normally. I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:631 (IPv4) I [09/Nov/2010:10:11:09 +] Listening to /var/run/cups/cups.sock (Domain) I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:443 (IPv4) W [09/Nov/2010:10:11:09 +] No limit for CUPS-Get-Document defined in policy default - using Send-Document's policy I [09/Nov/2010:10:11:09 +] Remote access is enabled. I [09/Nov/2010:10:11:09 +] Loaded configuration file "/etc/cups/cupsd.conf" I [09/Nov/2010:10:11:09 +] Using default TempDir of /var/spool/cups/tmp... I [09/Nov/2010:10:11:09 +] MaxClients limited to 1/3 (341) of the file descriptor limit (1024)... I [09/Nov/2010:10:11:09 +] Configured for up to 341 clients. I [09/Nov/2010:10:11:09 +] Allowing up to 10 client connections per host. I [09/Nov/2010:10:11:09 +] Using policy "default" as the default! I [09/Nov/2010:10:11:09 +] Full reload is required. I [09/Nov/2010:10:11:09 +] Loaded MIME database from "/usr/share/cups/mime" and "/etc/cups": 37 types, 73 filters... I [09/Nov/2010:10:11:09 +] Loading job cache file "/var/cache/cups/job.cache"... E [09/Nov/2010:10:11:09 +] [Job 4985] Unable to queue job for destination "leadpipe"! I [09/Nov/2010:10:11:09 +] Full reload complete. I [09/Nov/2010:10:11:09 +] Cleaning out old temporary files in "/var/spool/cups/tmp"... E [09/Nov/2010:10:11:09 +] Unable to remove temporary file "/var/spool/cups/tmp/.fontconfig" - Is a directory I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:631 on fd 6... I [09/Nov/2010:10:11:09 +] Listening to /var/run/cups/cups.sock on fd 7... I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:443 on fd 8... I [09/Nov/2010:10:11:09 +] Resuming new connection processing... E [09/Nov/2010:10:23:11 +] Unable to encrypt connection from - A TLS packet with unexpected length was received. 10:09:39 is the last time printers.conf is saved 10:10:00 scheduler shuts down (cause never seems to be mentioned for shut downs) 10:11:09 server back up, now missing printers (Unable to queue job for destination "leadpipe"!) Somewhere in this mess the printers.conf was removed or renamed and never replaced. Cups came back up with nil printers (which also leads to samba removing its record of the printers as well). The only possible culprit I can
[Touch-packages] [Bug 704546] Re: cups upstart script does not respawn
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/704546 Title: cups upstart script does not respawn Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups /etc/init/cups lacks a respawn line. For some reason cups has been crashing(I'll address that in another bug.). I expected upstart to respawn it. I checked the script, and it is missing the respawn line. I added the respawn line on my system. It works as expected. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: cups 1.4.4-6ubuntu2.3 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic x86_64 Architecture: amd64 Date: Tue Jan 18 11:29:36 2011 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/704546/+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 689368] Re: cups doesn't know ink levels but hplip provides them..
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/689368 Title: cups doesn't know ink levels but hplip provides them.. Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups 3 pdf's I was trying to print just failed for some unknown reason.. so I let cups troubleshoot the situation. When I saw the log it has the ink levels of both my cartidges. On cups gui I always get that ink levels aren't supported by my printer and currently I'm getting a status message that one of my cartidge is low on ink without specifying wich one when the info is easly obtainable. BTW the printer is a HP Deskjet F370 on ubuntu 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/689368/+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 790541] Re: cups and lprng cant be installed in paralell
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/790541 Title: cups and lprng cant be installed in paralell Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups We use both cups and lprng in paralell on our printserver for historical reasons. In hardy you could install them side-by-side, it was just lprng that conflicted with cupsys-client that conflicted with lprng. In lucid cups depends on cups-client, thus you can't realy just remove the client part and have them both. A better way would be to handle the conflicting client programs with the alternatives-system and be able to have them both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/790541/+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 816140] Re: Cups will not print its own test page, and will not print pdfs
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/816140 Title: Cups will not print its own test page, and will not print pdfs Status in cups package in Ubuntu: Expired Bug description: I have two printers configured in cups, an Epson Stylus Photo R2400 and an HP Laserjet 1200. The Laserjet works fine. I can drive the Epson satisfactorily using PhotoPrint with PhotoPrint's own colour correction. However, when I try to either run the Epson from applications (such as LightZone) which generate PDFs, or when I try to print CUPS' own test page, then it calls pdftoraster-poppler, and the following bad things happen: i) Unmodified, it uses the attached PPD, which (as you can see) refers to an sRGB colour profile that is stored somewhere on a Mac OSX filesystem. Quite correctly, it reports this as not found. Incidentally, if I run this ppd through cupstestppd, it says it can't find the sRGB profile, so someone hasn't been doing regression testing. ii) If I edit the PPD to point to the sRGB which I have on my system, then pdftoraster-poppler fails with a "Bogus memory allocation size" message. (Relevant portion of /var/log/cups/error.log attached). There are suggestions in the fora that I should make pdftoraster.poppler a symlink to pdftoraster, which calls ghostscript, but I get another error message if I do that (to the effect that gs can't find the default lab colour profile). In any case, I want pdftoraster-poppler to work, because it's part of the new colour corrected printing chain, which seems to me to be a good idea. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.3 ProcVersionSignature: Ubuntu 2.6.38-11.47-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 CheckboxSubmission: 2e1819d997bf66315c0605fd5b706346 CheckboxSystem: 91945207d732350068f2b1aa7b5d7083 Date: Mon Jul 25 22:06:32 2011 Lpstat: device for colour307: lpd://staffprint.dcs.qmul.ac.uk/colour307 device for Epson: ipp://192.168.0.4:631/printers/Epson device for laser415a: lpd://staffprint.dcs.qmul.ac.uk/laser415a device for laserjet: ipp://192.168.0.4:631/printers/laserjet device for PDF: cups-pdf:/ MachineType: Apple Computer, Inc. MacBook1,1 Papersize: a4 PpdFiles: laserjet: HP LaserJet 1300 - CUPS+Gutenprint v5.2.6 colour307: HP Color LaserJet v2013.114 Postscript (recommended) Epson: Epson Stylus Photo R2400 - CUPS+Gutenprint v5.2.6 PDF: Generic CUPS-PDF Printer laser415a: HP LaserJet 9040 Postscript (recommended) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=6e204b54-93e7-4eb5-9833-e24ef8ae69b6 ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to natty on 2011-05-20 (65 days ago) dmi.bios.date: 10/12/06 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MB11.88Z.0061.B03.0610121324 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208CC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMB11.88Z.0061.B03.0610121324:bd10/12/06:svnAppleComputer,Inc.:pnMacBook1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208CC8:rvrPVT:cvnAppleComputer,Inc.:ct10:cvrMac-F4208CC8: dmi.product.name: MacBook1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/816140/+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 836961] Re: CUPS setup hangs in synaptic
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/836961 Title: CUPS setup hangs in synaptic Status in cups package in Ubuntu: Expired Bug description: After a complete removal of CUPS and most of its dependencies, I'm trying to reinstall it via aptitude. However, every attempt I make ends in an infinite hang-up whenever aptitude (or synaptic) gets to "Setting up cups (1.4.6-5ubuntu1.3) ...". I'm using 11.04. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Mon Aug 29 15:48:23 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: letter ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=075766fd-0009-4649-9afe-8a01c86d080a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H55M Pro dmi.board.vendor: ASRock 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.:bvrP1.30:bd01/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. 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/836961/+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 856484] Re: Printing a PDF document to a Xerox 3300 Phase printer crashes the printer!!!
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/856484 Title: Printing a PDF document to a Xerox 3300 Phase printer crashes the printer!!! Status in cups package in Ubuntu: Expired Bug description: Printing a PDF from Document Viewer 2.32.0 on Natty crashes Xerox Phaser 3300 and it needs a reset for further printing. Adobe Acrobat reader can print though. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Thu Sep 22 18:58:13 2011 ExecutablePath: /usr/bin/evince ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-11-generic root=/dev/mapper/VLMain-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=ru_RU:en PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-11.48-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: Upgraded to natty on 2011-09-10 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/856484/+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 920702] Re: cups-config --ldflags lists a default -L searchpath
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/920702 Title: cups-config --ldflags lists a default -L searchpath Status in cups package in Ubuntu: Expired Bug description: On my 11.10 64bit box, I get this: $ cups-config --ldflags -L/usr/lib/x86_64-linux-gnu This library search path is default on the 64-bit system anyways. The negative effect is that this leads to my software build system (for samba) pulling in the libs that reside in /usr/lib/x86_64-linux-gnu too early. Specifically libtevent: current samba build has (and needs) a newer version of that library. Consequently, the symtem tevent library is linked (giving and error) instead of the built-in one. Arguably, this is also a bug in the samba-build system (that we will fix), in that the order of the -L<...> arguments to the gcc calls should be changed, but I still consider this listing of the default lib search path with -L wrong. Cheers - Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/920702/+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 913923] Re: Stapling and collating yields one staple through every copy
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/913923 Title: Stapling and collating yields one staple through every copy Status in cups package in Ubuntu: Expired Bug description: Hi, I have been using evince to print multiple PDFs of the same document to make class handouts. I have found by accident that I get what I want if I don't select the collate. (Each copy gets its own staple.) However, if I select the collate option, the whole pile of handouts gets stapled together. I am using a Canon IR-ADV-C5045-5051 PPD and a Canon C50501 ImageRunner printer. Thanks for hunting this down! ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cups 1.5.0-8ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CheckboxSubmission: b3f7c5231c874165f4d7945857608f87 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Mon Jan 9 10:46:45 2012 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: Dell Inc. Latitude D830 Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=e32a9aab-f506-4471-bb71-4b4e23ec3181 ro splash vga=794 nomodeset SourcePackage: cups UpgradeStatus: Upgraded to oneiric on 2012-01-04 (5 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T497J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/04/2010:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0T497J:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/913923/+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 881363] Re: second page doesnt print - samsung printer ml-1610
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/881363 Title: second page doesnt print - samsung printer ml-1610 Status in cups package in Ubuntu: Expired Bug description: second page of attached document does'nt print from Okular. red warning light of printer blinking. first page prints as expected. Attached document is uploaded here solely for analysing the technical issue. Copyright and other rights remain with the creator of the document (third party). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.4 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Tue Oct 25 13:08:35 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) Lpstat: device for ML-1610: usb://Samsung/ML-1610 MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P Papersize: letter PpdFiles: ML-1610: Samsung ML-1610 Foomatic/gdi ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-12-generic root=UUID=6d3afe7e-bc87-48b2-865d-8fe340037597 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 01GT.M026.20101220.RHU dmi.board.asset.tag: SAMSUNG dmi.board.name: N150P dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr01GT.M026.20101220.RHU:bd12/20/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: N150P dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/881363/+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 892356] Re: incorrect print-job return code on lexmark e250dn
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/892356 Title: incorrect print-job return code on lexmark e250dn Status in cups package in Ubuntu: Expired Bug description: printer started returning supplies-end-of-life messages (photoconductor) after installing ubuntu 11.04. both windows 7 and ununtu 10.10 correctly returns a job-complete message. printer manager page shows toner, photoconductor and maintenance-kit at good levels. changing toner and photoconductor did not clear the problem. the printer consistently shows this error. reinstalling the printer clears the red explanation-mark icon in the queue, but every print job will return the icon with the red '!'. problem occurs with proprietary and generic drivers. problem occurs with post-script and pcl drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/892356/+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 1796776] Re: package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un erro
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1796776 Title: package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post- installation guión el subproceso devolvió un error con estado de salida 5 Status in systemd package in Ubuntu: Invalid Bug description: i use photorec ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-systemd:amd64 237-3ubuntu10.3 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: Mon Oct 8 21:39:41 2018 ErrorMessage: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un error con estado de salida 5 InstallationDate: Installed on 2018-07-24 (76 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un error con estado de salida 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796776/+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 1796702] Re: Actualmente el arranque normal de ubuntu 18.04 se detiene en la posición indicada. Arranca normal en modo protegido. Muchas gracias.
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 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 1727356, 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. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1727356 Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) -- 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/1796702 Title: Actualmente el arranque normal de ubuntu 18.04 se detiene en la posición indicada. Arranca normal en modo protegido. Muchas gracias. Status in mutter package in Ubuntu: New Bug description: Normal start stops at:"Started user manager for vud 122" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 8 12:14:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 82945G/GZ Integrated Graphics Controller [1849:2772] InstallationDate: Installed on 2018-06-11 (118 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=es_UY:es PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=dceb6db0-13a5-4b39-932e-ffde095bd981 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: 945GCM-S dmi.board.vendor: ASRock 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.:bvrP1.20:bd02/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn945GCM-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 8 07:18:12 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1796702/+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 1796776] [NEW] package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un er
Public bug reported: i use photorec ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-systemd:amd64 237-3ubuntu10.3 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: Mon Oct 8 21:39:41 2018 ErrorMessage: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un error con estado de salida 5 InstallationDate: Installed on 2018-07-24 (76 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un error con estado de salida 5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1796776 Title: package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post- installation guión el subproceso devolvió un error con estado de salida 5 Status in systemd package in Ubuntu: New Bug description: i use photorec ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-systemd:amd64 237-3ubuntu10.3 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: Mon Oct 8 21:39:41 2018 ErrorMessage: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un error con estado de salida 5 InstallationDate: Installed on 2018-07-24 (76 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package libpam-systemd:amd64 237-3ubuntu10.3 failed to install/upgrade: instalado libpam-systemd:amd64 paquete post-installation guión el subproceso devolvió un error con estado de salida 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796776/+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 1579580] Re: ureadahead reports relative path errors in journalctl output
@Anders Hall You can rid of it by: systemctl stop ureadahead.service systemctl disable ureadahead.service apt-get purge ureadahead.service Reboot Check to see if it is running systemctl status ureadhead.service ps aux | grep ureadahead It should be gone. 18.10 is coming out in a few weeks. You can scrub your system and start anew. Download a 18.10 beta daily build and try it, or wait until release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
Attached is an updated version of the patch that builds. The previous one was failing because there's a test case that makes sure an "insert 2" of an IPv6 rule fails. That's enforcing the existence of the behavior that here we are arguing is a bug. ** Patch added: "Updated patch" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411/+attachment/5198885/+files/0005-lp1368411.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: New Status in ufw package in Ubuntu: Confirmed Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove
This bug was fixed in the package unattended-upgrades - 1.5ubuntu3 --- unattended-upgrades (1.5ubuntu3) cosmic; urgency=medium * Skip already adjusted packages from being checked for readjusting. This makes it clearer that the recursion ends and can also be a bit quicker. (LP: #1790687) * Fix PEP 8 warnings. Also ignore "W503 line break before binary operator" because it will become the best practice. * Don't crash on missing dpkg log file (LP: #1795692) * do_auto_remove() is successful unless a commit() operation fails (LP: #1795696) * Check only dowloaded .deb files for conffile prompts (LP: #1796100) -- Balint Reczey Sun, 07 Oct 2018 23:16:17 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795696 Title: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended- upgrade@1991:main:do_auto_remove Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795696/+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 1795692] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1991:main:get_dpkg_log_content
This bug was fixed in the package unattended-upgrades - 1.5ubuntu3 --- unattended-upgrades (1.5ubuntu3) cosmic; urgency=medium * Skip already adjusted packages from being checked for readjusting. This makes it clearer that the recursion ends and can also be a bit quicker. (LP: #1790687) * Fix PEP 8 warnings. Also ignore "W503 line break before binary operator" because it will become the best practice. * Don't crash on missing dpkg log file (LP: #1795692) * do_auto_remove() is successful unless a commit() operation fails (LP: #1795696) * Check only dowloaded .deb files for conffile prompts (LP: #1796100) -- Balint Reczey Sun, 07 Oct 2018 23:16:17 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795692 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1991:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/4c8953d6660713d8a064a29a86521b16d67e07ec 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795692/+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 1796100] Re: crashes while trying to open auxfiles as .deb
This bug was fixed in the package unattended-upgrades - 1.5ubuntu3 --- unattended-upgrades (1.5ubuntu3) cosmic; urgency=medium * Skip already adjusted packages from being checked for readjusting. This makes it clearer that the recursion ends and can also be a bit quicker. (LP: #1790687) * Fix PEP 8 warnings. Also ignore "W503 line break before binary operator" because it will become the best practice. * Don't crash on missing dpkg log file (LP: #1795692) * do_auto_remove() is successful unless a commit() operation fails (LP: #1795696) * Check only dowloaded .deb files for conffile prompts (LP: #1796100) -- Balint Reczey Sun, 07 Oct 2018 23:16:17 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1796100 Title: crashes while trying to open auxfiles as .deb Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: [Impact] unattended-upgrades does not work (reliably) in (bionic and) cosmic with the mirror:// method, as it tries to open the mirror file - which recent apt versions store in auxfiles - as a .deb: 2018-10-04 08:58:46,801 ERROR failed to read deb file /var/lib/apt/lists/auxfiles/_etc_apt_mirrors.list (E:Invalid archive signature) 2018-10-04 08:58:46,801 ERROR failed to read deb file /var/lib/apt/lists/auxfiles/_etc_apt_mirrors.list (E:Invalid archive signature) 2018-10-04 08:58:46,807 ERROR Apt returned an error, exiting 2018-10-04 08:58:46,807 ERROR error message: E:Invalid archive signature 2018-10-04 08:58:46,808 ERROR An error occurred: E:Invalid archive signature Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1595, in main install_start_time) File "/usr/bin/unattended-upgrade", line 1800, in run if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 860, in conffile_prompt deb = apt_inst.DebFile(destFile) apt_pkg.Error: E:Invalid archive signature [Test case] 1. Start with a not fully upgrades system, then configure it to use mirror:// : root@cc-apt:~# echo 'deb mirror+file:/etc/apt/mirrors.list cosmic main restricted' > /etc/apt/sources.list.d/mirrors-cosmic.list root@cc-apt:~# echo 'http://ftp.kfki.hu/linux/ubuntu/' > /etc/apt/mirrors.list root@cc-apt:~# echo 'Unattended-Upgrade::DevRelease "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-deb root@cc-apt:~# apt update Get:1 file:/etc/apt/mirrors.list Mirrorlist [33 B] Get:2 http://ftp.kfki.hu/linux/ubuntu cosmic InRelease [242 kB] ... Translation-en [73.7 kB] Fetched 27.1 MB in 10s (2812 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 280 packages can be upgraded. Run 'apt list --upgradable' to see them. 2. Clean downloaded files to make u-u redownload them: root@cc-apt:~# apt-get clean root@cc-apt:~# rm -f /var/lib/apt/lists/auxfiles/* 3. Run u-u and observe it crashing with the not fixed version and proceeding properly after the fix is applied. root@cc-apt:~# unattended-upgrade --dry-run Apt returned an error, exiting error message: E:Invalid archive signature Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2064, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1595, in main install_start_time) File "/usr/bin/unattended-upgrade", line 1800, in run if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 860, in conffile_prompt deb = apt_inst.DebFile(destFile) apt_pkg.Error: E:Invalid archive signature [Regression potential] The fix makes u-u check only files with .deb extension if they may raise configuration prompt. For supporting other file extensions the file name pattern will need to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1796100/+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 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the gnome freezes after GDM login. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1796758] [NEW] Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups
Public bug reported: Since the beginning of time, the way to apply changes to one's group memberships in UNIX has been to log out and log back in again. In current Ubuntu, that doesn't work. When you add yourself to a group, close all of your windows, log out, log back in again, and open a new gnome-terminal window, and your group memberships will be the same as before. This is because gnome-terminal processes are launched by gnome-terminal- server, which is launched by systemd --user, which doesn't exit when you log out. One possible fix would be to have the systemd init process (i.e., process 1) detect when group memberships have changed and re-launch the systemd --user processes for the users whose groups have changed. Another fix would be to kill systemd --user processes upon logout and have systemd re-launch them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 16:11:13 2018 InstallationDate: Installed on 2018-09-27 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW 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:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2018-09-27T11:40:55.615410 ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1796758 Title: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups Status in systemd package in Ubuntu: New Bug description: Since the beginning of time, the way to apply changes to one's group memberships in UNIX has been to log out and log back in again. In current Ubuntu, that doesn't work. When you add yourself to a group, close all of your windows, log out, log back in again, and open a new gnome-terminal window, and your group memberships will be the same as before. This is because gnome-terminal processes are launched by gnome- terminal-server, which is launched by systemd --user, which doesn't exit when you log out. One possible fix would be to have the systemd init process (i.e., process 1) detect when group memberships have changed and re-launch the systemd --user processes for the users whose groups have changed. Another fix would be to kill systemd --user processes upon logout and have systemd re-launch them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 16:11:13 2018 InstallationDate: Installed on 2018-09-27 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW 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:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th
[Touch-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user's supplementary groups )
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user's supplementary groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+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 1579580] Re: ureadahead reports relative path errors in journalctl output
Also getting these messages (trying to find useful information in syslog due to other issues, found these messages spamming). NVme as well. uname -a Linux computer 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux #journalctl -m | grep ureadahead | wc -l 30244 After cold boot: #journalctl -b | grep ureadahead | wc -l 892 @Khurshid Alam Does a workaround exist for getting rid of this on 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1796717] [NEW] Update to 0.69.0 next cycle
Public bug reported: The new version has new features and poppler updates require transition due to soname changes, that's for next cycle ** Affects: poppler (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: poppler (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1796717 Title: Update to 0.69.0 next cycle Status in poppler package in Ubuntu: Triaged Bug description: The new version has new features and poppler updates require transition due to soname changes, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1796717/+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 1796712] [NEW] libcurl3-gnutls in trusty fails to verify certificates when certificate chain is out-of-order
Public bug reported: libcurl3-gnutls 7.35.0-1ubuntu2.17 fails to verify remote certificate if the certificate chain provided is out-of-order. This is caused by libgnutls-dev package dependency, since libgnutls26 package is apparently long known to have this issue: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1373422 This bug can be observed with git, which depends on libcurl3-gnutls: git clone https://gnunet.org/git/libmicrohttpd.git/ Cloning into 'libmicrohttpd'... fatal: unable to access 'https://gnunet.org/git/libmicrohttpd.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none libgnutls28 package fixes this issue, since out-of-order certificate chains are allowed in that package. I am not very familiar with debian packaging process, so I was wondering if it is possible at all to bump dependency of libcurl3-gnutls from libgnutls-dev -> libgnutls28-dev for trusty. libgnutls28-dev conflicts with libgnutls-dev. At first sight, one of dependencies of libcurl3-gnutls-dev, lbrtmp-dev, also depends on libgnutls-dev. So, again I am not sure if this change is applicable or it causes nontrivial reverse-dependency issues. Given above bug filed against gnutls26 is still open after 4 years, I thought it might be easier to solve it on libcurl dependencies. (Is it?) Thanks. ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1796712 Title: libcurl3-gnutls in trusty fails to verify certificates when certificate chain is out-of-order Status in curl package in Ubuntu: New Bug description: libcurl3-gnutls 7.35.0-1ubuntu2.17 fails to verify remote certificate if the certificate chain provided is out-of-order. This is caused by libgnutls-dev package dependency, since libgnutls26 package is apparently long known to have this issue: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1373422 This bug can be observed with git, which depends on libcurl3-gnutls: git clone https://gnunet.org/git/libmicrohttpd.git/ Cloning into 'libmicrohttpd'... fatal: unable to access 'https://gnunet.org/git/libmicrohttpd.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none libgnutls28 package fixes this issue, since out-of-order certificate chains are allowed in that package. I am not very familiar with debian packaging process, so I was wondering if it is possible at all to bump dependency of libcurl3-gnutls from libgnutls-dev -> libgnutls28-dev for trusty. libgnutls28-dev conflicts with libgnutls-dev. At first sight, one of dependencies of libcurl3-gnutls-dev, lbrtmp-dev, also depends on libgnutls-dev. So, again I am not sure if this change is applicable or it causes nontrivial reverse-dependency issues. Given above bug filed against gnutls26 is still open after 4 years, I thought it might be easier to solve it on libcurl dependencies. (Is it?) Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1796712/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1758841 Title: virt-manager: Light grey menu items on light grey background are barely readable Status in ubuntu-themes package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu items in the toolbar are barely readable (cf screenshot) Background should be dark. virt-manager is the only application I found with this issue so far. [ Test case ] 1. Open virt-manager 2. Run a virtual machine 3. Click on the toolbar menu that can be opened from the power button 4. The items should be readable and have proper color [ Regression potential ] Menu items could not be visible in other dark menus --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:50:17 2018 InstallationDate: Installed on 2014-07-15 (1349 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: allSourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1795697] Re: Danish translation probably not synchronizing
the evolution-data-server/evolution issues have been fixed now (it was another of those cases where template sharing was enabled on launchpad leading to not have source files imported), I wouldn't be susprised if we still have buggy components in that case in cosmic... ** Changed in: evolution (Ubuntu) Importance: Undecided => Low ** Changed in: evolution (Ubuntu) Status: New => Fix Committed ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => High ** Changed in: evolution (Ubuntu) Importance: Low => High ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1795697 Title: Danish translation probably not synchronizing Status in Ubuntu Translations: New Status in evolution package in Ubuntu: Fix Committed Status in evolution-data-server package in Ubuntu: Fix Committed Status in gnome-font-viewer package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: EDIT: This has been fixed for gtk+; the bug has been marked as also affecting several other modules because they seem to have the same problem. The Danish translation here is not complete: https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details However we always fully translate GNOME upstream for each release, so it should be complete. Something is probably wrong with the import queue again. See also https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1795695 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1795697/+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 1796707] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: upgrade from 16.04 to 18.04 identified this bug during the installation process. Reported an unstable installation. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Mon Oct 8 10:16:43 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-07-19 (1907 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 third-party-packages -- 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/1796707 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: upgrade from 16.04 to 18.04 identified this bug during the installation process. Reported an unstable installation. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Mon Oct 8 10:16:43 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-07-19 (1907 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess 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/systemd/+bug/1796707/+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 1764087] Re: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37)
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/1764087 Title: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37) Status in X.Org X server: Won't Fix Status in lightdm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Apr 15 08:52:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+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 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
This bug was fixed in the package ubuntu-meta - 1.425 --- ubuntu-meta (1.425) cosmic; urgency=medium * Refreshed dependencies * Added xdg-desktop-portal-gtk to desktop-recommends (LP: #1795959) * Removed gdm3 from desktop [s390x] * Removed gnome-shell from desktop [s390x] * Removed ubuntu-session from desktop [s390x] -- Ken VanDine Thu, 04 Oct 2018 13:08:21 -0400 ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Security and MIR reviews have been completed for xdg-desktop-portal- gtk[1] and xdg-desktop-portal[2]. These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1796702] [NEW] Actualmente el arranque normal de ubuntu 18.04 se detiene en la posición indicada. Arranca normal en modo protegido. Muchas gracias.
Public bug reported: Normal start stops at:"Started user manager for vud 122" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 8 12:14:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 82945G/GZ Integrated Graphics Controller [1849:2772] InstallationDate: Installed on 2018-06-11 (118 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=es_UY:es PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=dceb6db0-13a5-4b39-932e-ffde095bd981 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: 945GCM-S dmi.board.vendor: ASRock 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.:bvrP1.20:bd02/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn945GCM-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 8 07:18:12 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1796702 Title: Actualmente el arranque normal de ubuntu 18.04 se detiene en la posición indicada. Arranca normal en modo protegido. Muchas gracias. Status in xorg package in Ubuntu: New Bug description: Normal start stops at:"Started user manager for vud 122" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 8 12:14:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 82945G/GZ Integrated Graphics Controller [1849:2772] InstallationDate: Installed on 2018-06-11 (118 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=es_UY:es PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=dceb6db0-13a5-4b39-932e-ffde095bd981 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: 945GCM-S dmi.board.vendor: ASRock 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:
[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy
If the systemd version doesn't support hybrid cgroup layout on xenial then fine but I thought it did. But please make sure that Xenial doesn't have anything mounted on /sys/fs/cgroup/unified. -- 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/1734410 Title: systemd: handle undelegated cgroup2 hierarchy Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Incomplete Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * When a container is presented with a unified cgroup hierarchy, which is not properly delegated, systemd should not attempt (and fail) to use. This improves compatibility of xenial containers running on unified cgroup hierarchy hosts. [Test Case] * Xenial containers should boot, with non-writable unified cgroup hierarchy hosts. [Regression Potential] * unified cgroup hierarchy is not in use by default on xenial hosts, thus this is forward compatibility improvment with e.g. bionic hosts running xenial containers. [Other Info] * Original bug report Hey everyone, Current systemd versions all fail when the unified cgroup hierarchy is not-writable. This is especially problematic in containers where the systemd administrator might decide to not delegate the unified hierarchy or when running with a liblxc driver that doesn't yet know how to handle the unified cgroup hierarchy. I've pushed patches to systemd upstream that let systemd ingnore the non-delegated unified hierarchy. The relevant commits are: e07aefbd675b651f8d45b5fb458f2747b04d6e04 2d56b80a1855836abf1d7458394c345ad9d55382 1ff654e28b7b8e7d0a0be33522a84069ac6b07c0 These patches will be in 236 but should be backported from xenial upwards. Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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 1734410] Re: systemd: handle undelegated cgroup2 hierarchy
I'm confused about this backport to xenial, given that xenial's mount- setup.c does not try to neither mount nor use /sys/fs/cgroup/unified. It wants to instead use /sys/fs/cgroup (for unified case). And it has no capability to use hybrid cgroups. Is this backport really needed back to xenial? I fear it may then require backporting cg_is_hybrid_wanted aka hybrid cgroup support as well. ** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => Incomplete -- 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/1734410 Title: systemd: handle undelegated cgroup2 hierarchy Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Incomplete Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * When a container is presented with a unified cgroup hierarchy, which is not properly delegated, systemd should not attempt (and fail) to use. This improves compatibility of xenial containers running on unified cgroup hierarchy hosts. [Test Case] * Xenial containers should boot, with non-writable unified cgroup hierarchy hosts. [Regression Potential] * unified cgroup hierarchy is not in use by default on xenial hosts, thus this is forward compatibility improvment with e.g. bionic hosts running xenial containers. [Other Info] * Original bug report Hey everyone, Current systemd versions all fail when the unified cgroup hierarchy is not-writable. This is especially problematic in containers where the systemd administrator might decide to not delegate the unified hierarchy or when running with a liblxc driver that doesn't yet know how to handle the unified cgroup hierarchy. I've pushed patches to systemd upstream that let systemd ingnore the non-delegated unified hierarchy. The relevant commits are: e07aefbd675b651f8d45b5fb458f2747b04d6e04 2d56b80a1855836abf1d7458394c345ad9d55382 1ff654e28b7b8e7d0a0be33522a84069ac6b07c0 These patches will be in 236 but should be backported from xenial upwards. Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
** Description changed: [Impact] - /var/log's Permission is going back to 755 - after upgrading systemd - if there are rsyslog's configuration on /var/lib/tmpfiles.d/ + /var/log's Permission is going back to 755 after upgrading systemd + if rsyslog is installed (default) - Affected X, A, B, C + [Resolution] + Ensure that dh_installinit does not "helpfully" generate partial systemd-tmpfiles snippets in systemd package postinst. - This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. - after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) - so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 + Ensure that a generic systemd-tmpfiles call is done in systemd postinst, + which takes into account /all/ configurations, not just some. [Test Case] - 1. deploy 16.04 vm - 2. check ll /var (775) + 1. Launch xenila container + 2. ls -latr /var 3. apt install --reinstall systemd - 4. check ll /var (755) + 4. ls -latr /var - [Regression Potential] - This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. - - [Others] - - For this issue, need to fix below pkgs - - debhelper - systemd ( rebuilding with new debhelper is needed ) - rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) - - [Original description] - - Upgrading or reinstalling the systemd package when using rsyslogd - results in bad permissions (0755 instead of 0775) being set on - /var/log/. As a consequence of this, rsyslogd can no longer create new - files within this directory, resulting in lost log messages. - - The default configuration of rsyslogd provided by Ubuntu runs the daemon - as syslog:syslog and sets ownership of /var/log to syslog:adm with mode - 0775. - - Systemd's default tmpfiles configuration sets /var/log to 0755 in - /usr/lib/tmpfiles.d/var.conf, however this is overridden in - /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. - - It looks as though an upgrade of the systemd package fails to take - /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. - This results in /var/log receiving mode 0755 instead of the expected - 0775: - - nick @ log2.be1.ams1:~ $ lsb_release -a - No LSB modules are available. - Distributor ID: Ubuntu - Description: Ubuntu 16.04.3 LTS - Release: 16.04 - Codename: xenial - - nick @ log2.be1.ams1:~ $ apt policy systemd - systemd: - Installed: 229-4ubuntu21.1 - Candidate: 229-4ubuntu21.1 - Version table: - *** 229-4ubuntu21.1 500 - 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages - 100 /var/lib/dpkg/status - 229-4ubuntu4 500 - 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages - - nick @ log2.be1.ams1:~ $ apt policy rsyslog - rsyslog: - Installed: 8.16.0-1ubuntu3 - Candidate: 8.16.0-1ubuntu3 - Version table: - *** 8.16.0-1ubuntu3 500 - 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status - - nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf - d /var/log 0755 - - - - f /var/log/wtmp 0664 root utmp - - f /var/log/btmp 0600 root utmp - - - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf - # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by - # the syslog group, so that rsyslog can run as user. - # See tmpfiles.d(5) for details. - - # Type PathMode UID GID Age Argument - d /var/log 0775 root syslog - - - nick @ log2.be1.ams1:~ $ ls -ld /var/log - drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log - - nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd - Reading package lists... Done - Building dependency tree - Reading state information... Done - 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. - Need to get 3,634 kB of archives. - After this operation, 0 B of additional disk space will be used. - Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu21.1 [3,634 kB] - Fetched 3,634 kB in 0s (24.3 MB/s) - (Reading database ... 86614 files and directories currently installed.) - Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ... - Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ... - Processing triggers for
[Touch-packages] [Bug 1689833] Re: OpenVPN server does not start properly on boot
@jnx, the 192.168.11.254 address you are trying to bind to, is that the normal nic of that machine? Or something else, like a wifi interface, or something that would only come up after the user logs in, assuming this is a desktop? -- 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/1689833 Title: OpenVPN server does not start properly on boot Status in openvpn package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: OpenVPN intermittently fails to bind to local address during boot on Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does not. /var/log/openvpn.log Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:02 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address [AF_INET]192.168.4.254:1194: Cannot assign requested address Wed May 10 15:42:02 2017 Exiting due to fatal error In case it does not start, running 'sudo service openvpn start' fixes that problem. /var/log/openvpn.log Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:43 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 HWADDR=52:54:00:f0:26:0c Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100 Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500 Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 172.16.1.2 Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2 Wed May 10 15:42:43 2017 GID set to nogroup Wed May 10 15:42:43 2017 UID set to nobody Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194 Wed May 10 15:42:43 2017 UDPv4 link remote: [undef] Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256 Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0 Wed May 10 15:42:43 2017 IFCONFIG POOL LIST Wed May 10 15:42:43 2017 Initialization Sequence Completed My guess is that systemd starts OpenVPN too early before the network is brought up sufficiently. Running 'sudo systemctl edit --full openvpn' and adding 'Wants=network-online.target' does not change that behaviour. user@server:~$ sudo systemd-analyze critical-chain graphical.target @2.160s └─multi-user.target @2.159s └─ntp.service @2.054s +104ms └─remote-fs.target @2.052s └─remote-fs-pre.target @2.052s └─open-iscsi.service @1.993s +57ms └─iscsid.service @1.942s +47ms └─network-online.target @1.941s └─network.target @1.929s └─networking.service @1.793s +134ms └─apparmor.service @1.140s +395ms └─local-fs.target @1.140s └─local-fs-pre.target @1.139s └─lvm2-monitor.service @602ms +536ms └─lvm2-lvmetad.service @773ms └─systemd-journald.socket @574ms └─-.slice @500ms The boot time is quite short. Clean install with the additional packages ntp and openssh-server. This happens both on bare metal and as a Virtual Machine (KVM) as well. /etc/openvpn/server.conf local 192.168.4.254 port 1194 proto udp dev tun ca ./easy-rsa/keys/ca.crt cert ./easy-rsa/keys/crt.crt key ./easy-rsa/keys/key.key dh ./easy-rsa/keys/dh2048.pem tls-auth
[Touch-packages] [Bug 1796693] [NEW] PCI/internal sound card not detected
Public bug reported: I can't hear anything. And in the settings isn't any device like speaker or headphones. I run Ubuntu on ASUS X205TA. Thank you so much for your help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.10.0-041000-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Oct 8 16:51:54 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X205TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1796693 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I can't hear anything. And in the settings isn't any device like speaker or headphones. I run Ubuntu on ASUS X205TA. Thank you so much for your help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.10.0-041000-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Oct 8 16:51:54 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X205TA 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/1796693/+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 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
** Changed in: systemd (Ubuntu Xenial) Status: Triaged => In Progress -- 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: In Progress Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => In Progress -- 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1796355] Re: USB-C ValueLine network adapter fails to connect
There's something wrong going on here. I first reported this issue as a 'linux' bug, based on a hasty reading of documentation. I never finished that report, so I expect that to be incomplete. Shortly afterwards I re-reported it as a probable NetworkManager issue. It seems that these two issues have got the same #number. Any confusion about whether this is confirmed or not is, I'm afraid of your own making. -- 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/1796355 Title: USB-C ValueLine network adapter fails to connect Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: The adapter I'm trying to use using is a 'Valueline' USB-C adapter, with no external identifying information. lsusb lists it as Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp. It works fine on a Windows 10 system (same hardware platform), where it's identified as a 10/100/1000 Realtek adapter. When I connect it to my system (Asus Zenbook UX490UA) internal lights go on, but no connection is produced. The network icon (upper right) is shown briefly, then disappears, the is show, then disappears. After some time it seems to give up. Kernel logs show repeated occurrences of: Oct 5 17:02:22 athasus kernel: [ 317.843590] usb 4-2: new SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 317.863719] usb 4-2: New USB device found, idVendor=0bda, idProduct=8153 Oct 5 17:02:22 athasus kernel: [ 317.863728] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Oct 5 17:02:22 athasus kernel: [ 317.863735] usb 4-2: Product: USB 10/100/1000 LAN Oct 5 17:02:22 athasus kernel: [ 317.863741] usb 4-2: Manufacturer: Realtek Oct 5 17:02:22 athasus kernel: [ 317.863745] usb 4-2: SerialNumber: 0100 Oct 5 17:02:22 athasus kernel: [ 318.000268] usb 4-2: reset SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 318.057875] r8152 4-2:1.0 eth0: v1.09.9 Oct 5 17:02:22 athasus kernel: [ 318.138042] r8152 4-2:1.0 enxa0cec809bf58: renamed from eth0 Oct 5 17:02:22 athasus kernel: [ 318.170397] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.176359] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.354745] r8152 4-2:1.0 enxa0cec809bf58: Stop submitting intr, status -71 Oct 5 17:02:22 athasus kernel: [ 318.543737] usb 4-2: USB disconnect, device number 121 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 17:35:17 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-03 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE ATH 79577e92-4b01-46c4-bbff-2088aaf0750a wifi 1538753528 fre 5 okt 2018 17:32:08 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 ATH 79577e92-4b01-46c4-bbff-2088aaf0750a /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable
I tested this package: $ sha1sum light-themes_16.10+18.04.20181005-0ubuntu1_all.deb d05d75088b41c7594bf3e4e32879d8950983caec light-themes_16.10+18.04.20181005-0ubuntu1_all.deb And the bug is indeed fixed for me in virt-manager. -- 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/1758841 Title: virt-manager: Light grey menu items on light grey background are barely readable Status in ubuntu-themes package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu items in the toolbar are barely readable (cf screenshot) Background should be dark. virt-manager is the only application I found with this issue so far. [ Test case ] 1. Open virt-manager 2. Run a virtual machine 3. Click on the toolbar menu that can be opened from the power button 4. The items should be readable and have proper color [ Regression potential ] Menu items could not be visible in other dark menus --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:50:17 2018 InstallationDate: Installed on 2014-07-15 (1349 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: allSourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1762385] Re: dell_wmi: Unknown key codes
** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => In Progress -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => In Progress -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: In Progress Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => In Progress -- 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+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 1487679] Re: Breaking ordering cycle by deleting job NetworkManager.service/start
** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => New -- 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/1487679 Title: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in avahi package in Ubuntu: Confirmed Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in rpcbind package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in avahi source package in Xenial: Confirmed Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: Confirmed Status in nfs-utils source package in Xenial: Confirmed Status in rpcbind source package in Xenial: Confirmed Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: Confirmed Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+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 1727237] Re: systemd-resolved is not finding a domain
** Changed in: systemd (Ubuntu Artful) Status: Triaged => Won't Fix -- 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/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Triaged Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * Certain WiFi captive portals do not support EDNS0 queries, as per RFC. * Instead of responding with the captive portal IP address, they resond with domain not found * This prevents the user from hitting the captive portal login page, able to authenticate, and gain access to the internets. [The Fix] * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried with EDNS0 * And receiving the right response without EDNS0 * The solution was to downgrade transactions, and retry EDNS0 + NXDOMAIN result without EDNS0 with a hope of getting the right answer. [Test Case] * systemd-resolve securelogin.example.com * journalctl -b -u systemd-resolve | grep DVE-2018 You should obverse that a warning message that transaction was retried with a reduced feature level e.g. UDP or TCP. After this test case is performed the result will be cached, therefore to revert to pristine state perform * systemd-resolve --flush-caches [Regression Potential] * The code retries, and then caches, NXDOMAIN results for certain queries (those that have 'secure' in them) with and without EDNS0. * Thus initial query for these domains may take longer, but hopefully will manage to receive the correct response. * Manufacturers are encouraged to correctly support EDNS0 queries, with flag D0 set to zero. [Other Info] * This issue is tracked as a dns-violation at https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md [Original Bug report] I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable
Hello Jean-Baptiste, or anyone else affected, Accepted ubuntu-themes into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-themes (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1758841 Title: virt-manager: Light grey menu items on light grey background are barely readable Status in ubuntu-themes package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu items in the toolbar are barely readable (cf screenshot) Background should be dark. virt-manager is the only application I found with this issue so far. [ Test case ] 1. Open virt-manager 2. Run a virtual machine 3. Click on the toolbar menu that can be opened from the power button 4. The items should be readable and have proper color [ Regression potential ] Menu items could not be visible in other dark menus --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:50:17 2018 InstallationDate: Installed on 2014-07-15 (1349 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: allSourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1743373] Re: Combobox arrow and color are inverted
I can confirm the issue is fixed in Cosmic beta. Thanks! -- 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/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Test case ] Comobobox lists extenders use invalid arrows 1. Both at the top and at the bottom, the arrow (triangle) points downwards. 2. Colors of sensitive and insensitive arrows are swapped. [ Test case ] 1. Open gnome-terminal, in menu goes to: Edit -> Profile Preferences -> Compatibility -> Encoding 2. The arrow at the top should point upwards 3. Tha arrow at the bottom should point downwards 4. Arrows should be visible only when there's actually something to scroll up or down. [ Regression potential ] Arrows aren't shown as expected in menus or combo-box --- Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: allSourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1750780] Re: Race with local file systems can make open-vm-tools fail to start
So, is there anything requested to be done with Xenial's systemd in this bug? ** Changed in: systemd (Ubuntu Xenial) Status: New => Incomplete -- 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/1750780 Title: Race with local file systems can make open-vm-tools fail to start Status in cloud-init: Invalid Status in open-vm-tools package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in open-vm-tools source package in Xenial: Fix Released Status in systemd source package in Xenial: Incomplete Status in open-vm-tools source package in Artful: Fix Released Status in open-vm-tools package in Debian: Fix Released Bug description: Since the change in [1] open-vm-tools-service starts very (very) early. Not so much due to the Before=cloud-init-local.service But much more by DefaultDependencies=no That can trigger an issue that looks like root@ubuntuguest:~# systemctl status -l open-vm-tools.service ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor preset: enabled) Active: failed (Result: resources) As it is right now open-vm-tools can race with the other early start and then fail. In detail one can find a message like: open-vm-tools.service: Failed to run 'start' task: Read-only file system" This is due to privtaeTmp=yes which is also set needing a writable /var/tmp [2] To ensure this works PrivateTmp would have to be removed (not good) or some after dependencies added that make this work reliably. I added After=local-fs.target which made it work for me in 3/3 tests. I' like to have an ack by the cloud-init Team that this does not totally kill the originally intended Before=cloud-init-local.service I think it does not as local-fs can complete before cloud-init-local, then open-vm-tools can initialize and finally cloud-init-local can pick up the data. To summarize: # cloud-init-local # DefaultDependencies=no Wants=network-pre.target After=systemd-remount-fs.service Before=NetworkManager.service Before=network-pre.target Before=shutdown.target Before=sysinit.target Conflicts=shutdown.target RequiresMountsFor=/var/lib/cloud # open-vm-tools # DefaultDependencies=no Before=cloud-init-local.service Proposed is to add to the latter: After=local-fs.target [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677 [2]: https://github.com/systemd/systemd/issues/5610 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1743373] Re: Combobox arrow and color are inverted
Hello Egmont, or anyone else affected, Accepted ubuntu-themes into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-themes (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Test case ] Comobobox lists extenders use invalid arrows 1. Both at the top and at the bottom, the arrow (triangle) points downwards. 2. Colors of sensitive and insensitive arrows are swapped. [ Test case ] 1. Open gnome-terminal, in menu goes to: Edit -> Profile Preferences -> Compatibility -> Encoding 2. The arrow at the top should point upwards 3. Tha arrow at the bottom should point downwards 4. Arrows should be visible only when there's actually something to scroll up or down. [ Regression potential ] Arrows aren't shown as expected in menus or combo-box --- Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: allSourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1761684] Re: Regression in lists like gnome-boxes
Hello Didier, or anyone else affected, Accepted ubuntu-themes into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: gnome-boxes (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-themes (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-themes (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1761684 Title: Regression in lists like gnome-boxes Status in gnome-boxes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Status in gnome-boxes source package in Bionic: New Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] The theme regressed the actively selected item on gnome-boxes (hover is also hard to read). See attached screenshot. [ Test case ] 1. Run gnome-boxes (install the same package if not available) 2. Click on "New" box button 3. The first page should show a list of available machines, content should be readable. [ Regression potential ] Other gnome-boxes lists are not properly themed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1781736] Re: Buttons aren't properly themed in Radiance theme under HiDPI
Hello Harm, or anyone else affected,
Accepted ubuntu-themes into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: ubuntu-themes (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
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/1781736
Title:
Buttons aren't properly themed in Radiance theme under HiDPI
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
Fix Released
Status in ubuntu-themes source package in Bionic:
Fix Committed
Bug description:
[ Impact ]
Buttons in radiance aren't properly themed in highdpi mode
[ Test case ]
1. Run a gtk app with CSD (i.e.) gnome-disks with GDK_SCALE=2 and
GTK_THEME=Radiance
GDK_SCALE=2 GTK_THEME=Radiance gnome-disks
2. Buttons should be properly themed and with high-quality borders in both
normal and
focused state.
[ Regression potential ]
No proper borders are painted on buttons under Radiance
--
There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
widgets.css that causes focused buttons to be drawn incorrectly in the
radiance theme. The following change should be made to the file to fix
the incorrect assets link:
118c118
< url("assets/button-focused.png@2"));
---
> url("assets/button-focu...@2.png"));
ProblemType: BugDistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified:
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
Uname: Linux 4.15.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Jul 14 15:41:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-06-23 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: allSourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+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
Hello Jeremy, or anyone else affected, Accepted ubuntu-themes into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-themes (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed 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. Regression Potential Color for elements other than the label of suggested actions is wrong 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/+source/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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
Hello Nate, or anyone else affected,
Accepted ubuntu-themes into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: ubuntu-themes (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
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/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in ubuntu-themes package in Ubuntu:
Fix Released
Status in ubuntu-themes source package in Bionic:
Fix Committed
Bug description:
[ Impact ]
Running an application with Radiance theme shows an error
[ Test case ]
1. Run an application (evince) in terminal using Radiance:
GTK_THEME=Radiance evince
2. No error should be spotted regarding a missing .css file
[ Regression potential ]
None
---
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: BugDistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: allSourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1773045/+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 1782038] Re: Window buttons are small in a maximized Chromium window
Hello Thomas, or anyone else affected, Accepted ubuntu-themes into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-themes (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1782038 Title: Window buttons are small in a maximized Chromium window Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] In maximized google-chrome / chromium window buttons for close, minimize, and restore buttons should be normal-sized, but instead appear small. [ Test case ] 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium or Google Chrome window. 3. Ensure that in chrome settings, the "Use system borders" option is unchecked 4. Maximize. 5. Window buttons should have normal size. [ Regression potential ] Other windows buttons could loose the padding used for being closed. --- Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1795895] Re: Accelerators on selected menu-items are not readable
Hello Marco, or anyone else affected, Accepted ubuntu-themes into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- themes/16.10+18.04.20181005-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: ubuntu-themes (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-themes (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1795895 Title: Accelerators on selected menu-items are not readable Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] As visible in the attached screenshot in the nautilus context menu, the accelerator is not readable when the item is selected: https://i.imgur.com/xabntIH.png [ Test case ] 1. Open Nautilus 2. Right-click on the files view 3. Select an item with an accelerator 4. The accelerator should be visible (white in Ambiance theme) [ Possible regressions ] Accelerators on menuitems on menubars might always be painted as when hovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1743373] Re: Combobox arrow and color are inverted
** Also affects: ubuntu-themes (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Test case ] Comobobox lists extenders use invalid arrows 1. Both at the top and at the bottom, the arrow (triangle) points downwards. 2. Colors of sensitive and insensitive arrows are swapped. [ Test case ] 1. Open gnome-terminal, in menu goes to: Edit -> Profile Preferences -> Compatibility -> Encoding 2. The arrow at the top should point upwards 3. Tha arrow at the bottom should point downwards 4. Arrows should be visible only when there's actually something to scroll up or down. [ Regression potential ] Arrows aren't shown as expected in menus or combo-box --- Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: allSourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1762385] Re: dell_wmi: Unknown key codes
** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 Bionic) Importance: Undecided Status: New -- 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-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed 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. Regression Potential Color for elements other than the label of suggested actions is wrong 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/+source/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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Confirmed Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]
I think tlp was responsible for the issue, as after uninstalling it, I could not reproduce it consistently (only happens very rarely). -- 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/1788807 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. ProblemType: Bug
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files
** Changed in: initramfs-tools Status: Confirmed => Fix Released -- 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/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files Status in initramfs-tools: Fix Released Status in Ubuntu Software Center: Invalid Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
The attachment "0005-lp1368411.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: New Status in ufw package in Ubuntu: Confirmed Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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 1761684] Re: Regression in lists like gnome-boxes
This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1 --- ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium [ Khurshid Alam ] * Remove nonexistent gnome-builder.css (LP: #1773045) [ Marco Trevisan (Treviño) ] * Radiance: fix typo in assets link for focused buttons (LP: #1781736) * Radiance: Use scaled image for buttons border (LP: #1781736) * Ambiance, Radiance: don't use padding on window buttons for chromium (LP: #1782038) * Ambiance: use default foreground color for toolbar menus (LP: #1758841) * Ambiance, Radiance: show proper arrow in combobox (LP: #1743373) * Ambiance, Radiance: use default disabled color for actions headerbar buttons (LP: #1785699) * Ambiace, Radiance: use headerbar destructive-action definition for buttons * Ambiance, Radiance: fix list selected color for gnome-boxes (LP: #1761684) * Ambiance, Radiance: properly theme disabled and hovered accelerators (LP: #1795895) -- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- 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/1761684 Title: Regression in lists like gnome-boxes Status in gnome-boxes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: [ Impact ] The theme regressed the actively selected item on gnome-boxes (hover is also hard to read). See attached screenshot. [ Test case ] 1. Run gnome-boxes (install the same package if not available) 2. Click on "New" box button 3. The first page should show a list of available machines, content should be readable. [ Regression potential ] Other gnome-boxes lists are not properly themed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1796671] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: install error i guess ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Sun Oct 7 17:23:55 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-12-01 (1771 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-10-08 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 third-party-packages -- 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/1796671 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: install error i guess ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 Date: Sun Oct 7 17:23:55 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-12-01 (1771 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-10-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796671/+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 1671951] Re: networkd should allow configuring IPV6 MTU
** Description changed: + = systemd = + + [Impact] + + * IPv6 traffic failing to send/receive due to incompatible/low MTU + setting. Specifically, IPv6 traffic may have higher MTU requirements + than IPv4 traffic and thus may need to be overridden and/or set to a + higher value than IPv6 traffic. + + [Test Case] + + * Use IPv6MTUBytes= setting in a .network unit + * Restart systemd-network + * Check that there no error messages / warnings about not-recognizing this option + * Check that MTU bytes, is at least IPv6MTUBytes on the interface + + [Regression Potential] + + * This is a future compatible backport of an additional keyword not + used by default. It may result in MTU change to a higher value, which + should not cause loss of connectivity. + + [Other Info] + + * Original bug report below + + = end of systemd = + 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. - Some context from those discussions - >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. - Yes. Anything that creates a PMTUD black hole can result in + Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. - One example here is egress from an ipsec tunnel wherein the next + One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. - In essence, any of these sort of cases that require an explicit + In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: In Progress Bug description: = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Description changed: + [Impact] + + * core18 systems fail to update hostname + * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname + + [Test Case] + + * run a core18 system, check that dhcp acquire hostname is correctly + updated in /etc/writable/hostname + + [Regression Potential] + + * This is cherrypick of code that has gone missing since xenial. + * There is no change of behaviour for the classic systems. + * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. + + [Other Info] + + * original bug report + The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. -- 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
This bug was fixed in the package ubuntu-themes -
16.10+18.10.20181005-0ubuntu1
---
ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium
[ Khurshid Alam ]
* Remove nonexistent gnome-builder.css (LP: #1773045)
[ Marco Trevisan (Treviño) ]
* Radiance: fix typo in assets link for focused buttons (LP: #1781736)
* Radiance: Use scaled image for buttons border (LP: #1781736)
* Ambiance, Radiance: don't use padding on window buttons for chromium
(LP: #1782038)
* Ambiance: use default foreground color for toolbar menus (LP:
#1758841)
* Ambiance, Radiance: show proper arrow in combobox (LP: #1743373)
* Ambiance, Radiance: use default disabled color for actions headerbar
buttons (LP: #1785699)
* Ambiace, Radiance: use headerbar destructive-action definition for
buttons
* Ambiance, Radiance: fix list selected color for gnome-boxes (LP:
#1761684)
* Ambiance, Radiance: properly theme disabled and hovered accelerators
(LP: #1795895)
-- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07
+
** Changed in: ubuntu-themes (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in ubuntu-themes package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
Running an application with Radiance theme shows an error
[ Test case ]
1. Run an application (evince) in terminal using Radiance:
GTK_THEME=Radiance evince
2. No error should be spotted regarding a missing .css file
[ Regression potential ]
None
---
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: BugDistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: allSourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1773045/+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 1782038] Re: Window buttons are small in a maximized Chromium window
This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1 --- ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium [ Khurshid Alam ] * Remove nonexistent gnome-builder.css (LP: #1773045) [ Marco Trevisan (Treviño) ] * Radiance: fix typo in assets link for focused buttons (LP: #1781736) * Radiance: Use scaled image for buttons border (LP: #1781736) * Ambiance, Radiance: don't use padding on window buttons for chromium (LP: #1782038) * Ambiance: use default foreground color for toolbar menus (LP: #1758841) * Ambiance, Radiance: show proper arrow in combobox (LP: #1743373) * Ambiance, Radiance: use default disabled color for actions headerbar buttons (LP: #1785699) * Ambiace, Radiance: use headerbar destructive-action definition for buttons * Ambiance, Radiance: fix list selected color for gnome-boxes (LP: #1761684) * Ambiance, Radiance: properly theme disabled and hovered accelerators (LP: #1795895) -- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- 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/1782038 Title: Window buttons are small in a maximized Chromium window Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: [ Impact ] In maximized google-chrome / chromium window buttons for close, minimize, and restore buttons should be normal-sized, but instead appear small. [ Test case ] 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium or Google Chrome window. 3. Ensure that in chrome settings, the "Use system borders" option is unchecked 4. Maximize. 5. Window buttons should have normal size. [ Regression potential ] Other windows buttons could loose the padding used for being closed. --- Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1781736] Re: Buttons aren't properly themed in Radiance theme under HiDPI
This bug was fixed in the package ubuntu-themes -
16.10+18.10.20181005-0ubuntu1
---
ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium
[ Khurshid Alam ]
* Remove nonexistent gnome-builder.css (LP: #1773045)
[ Marco Trevisan (Treviño) ]
* Radiance: fix typo in assets link for focused buttons (LP: #1781736)
* Radiance: Use scaled image for buttons border (LP: #1781736)
* Ambiance, Radiance: don't use padding on window buttons for chromium
(LP: #1782038)
* Ambiance: use default foreground color for toolbar menus (LP:
#1758841)
* Ambiance, Radiance: show proper arrow in combobox (LP: #1743373)
* Ambiance, Radiance: use default disabled color for actions headerbar
buttons (LP: #1785699)
* Ambiace, Radiance: use headerbar destructive-action definition for
buttons
* Ambiance, Radiance: fix list selected color for gnome-boxes (LP:
#1761684)
* Ambiance, Radiance: properly theme disabled and hovered accelerators
(LP: #1795895)
-- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07
+
** Changed in: ubuntu-themes (Ubuntu)
Status: In Progress => Fix Released
--
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/1781736
Title:
Buttons aren't properly themed in Radiance theme under HiDPI
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
Buttons in radiance aren't properly themed in highdpi mode
[ Test case ]
1. Run a gtk app with CSD (i.e.) gnome-disks with GDK_SCALE=2 and
GTK_THEME=Radiance
GDK_SCALE=2 GTK_THEME=Radiance gnome-disks
2. Buttons should be properly themed and with high-quality borders in both
normal and
focused state.
[ Regression potential ]
No proper borders are painted on buttons under Radiance
--
There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
widgets.css that causes focused buttons to be drawn incorrectly in the
radiance theme. The following change should be made to the file to fix
the incorrect assets link:
118c118
< url("assets/button-focused.png@2"));
---
> url("assets/button-focu...@2.png"));
ProblemType: BugDistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified:
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
Uname: Linux 4.15.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Jul 14 15:41:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-06-23 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: allSourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+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 1743373] Re: Combobox arrow and color are inverted
This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1 --- ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium [ Khurshid Alam ] * Remove nonexistent gnome-builder.css (LP: #1773045) [ Marco Trevisan (Treviño) ] * Radiance: fix typo in assets link for focused buttons (LP: #1781736) * Radiance: Use scaled image for buttons border (LP: #1781736) * Ambiance, Radiance: don't use padding on window buttons for chromium (LP: #1782038) * Ambiance: use default foreground color for toolbar menus (LP: #1758841) * Ambiance, Radiance: show proper arrow in combobox (LP: #1743373) * Ambiance, Radiance: use default disabled color for actions headerbar buttons (LP: #1785699) * Ambiace, Radiance: use headerbar destructive-action definition for buttons * Ambiance, Radiance: fix list selected color for gnome-boxes (LP: #1761684) * Ambiance, Radiance: properly theme disabled and hovered accelerators (LP: #1795895) -- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- 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/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: [ Test case ] Comobobox lists extenders use invalid arrows 1. Both at the top and at the bottom, the arrow (triangle) points downwards. 2. Colors of sensitive and insensitive arrows are swapped. [ Test case ] 1. Open gnome-terminal, in menu goes to: Edit -> Profile Preferences -> Compatibility -> Encoding 2. The arrow at the top should point upwards 3. Tha arrow at the bottom should point downwards 4. Arrows should be visible only when there's actually something to scroll up or down. [ Regression potential ] Arrows aren't shown as expected in menus or combo-box --- Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: allSourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable
This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1 --- ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium [ Khurshid Alam ] * Remove nonexistent gnome-builder.css (LP: #1773045) [ Marco Trevisan (Treviño) ] * Radiance: fix typo in assets link for focused buttons (LP: #1781736) * Radiance: Use scaled image for buttons border (LP: #1781736) * Ambiance, Radiance: don't use padding on window buttons for chromium (LP: #1782038) * Ambiance: use default foreground color for toolbar menus (LP: #1758841) * Ambiance, Radiance: show proper arrow in combobox (LP: #1743373) * Ambiance, Radiance: use default disabled color for actions headerbar buttons (LP: #1785699) * Ambiace, Radiance: use headerbar destructive-action definition for buttons * Ambiance, Radiance: fix list selected color for gnome-boxes (LP: #1761684) * Ambiance, Radiance: properly theme disabled and hovered accelerators (LP: #1795895) -- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- 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/1758841 Title: virt-manager: Light grey menu items on light grey background are barely readable Status in ubuntu-themes package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Bug description: [ Impact ] With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu items in the toolbar are barely readable (cf screenshot) Background should be dark. virt-manager is the only application I found with this issue so far. [ Test case ] 1. Open virt-manager 2. Run a virtual machine 3. Click on the toolbar menu that can be opened from the power button 4. The items should be readable and have proper color [ Regression potential ] Menu items could not be visible in other dark menus --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:50:17 2018 InstallationDate: Installed on 2014-07-15 (1349 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: allSourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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
This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1 --- ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium [ Khurshid Alam ] * Remove nonexistent gnome-builder.css (LP: #1773045) [ Marco Trevisan (Treviño) ] * Radiance: fix typo in assets link for focused buttons (LP: #1781736) * Radiance: Use scaled image for buttons border (LP: #1781736) * Ambiance, Radiance: don't use padding on window buttons for chromium (LP: #1782038) * Ambiance: use default foreground color for toolbar menus (LP: #1758841) * Ambiance, Radiance: show proper arrow in combobox (LP: #1743373) * Ambiance, Radiance: use default disabled color for actions headerbar buttons (LP: #1785699) * Ambiace, Radiance: use headerbar destructive-action definition for buttons * Ambiance, Radiance: fix list selected color for gnome-boxes (LP: #1761684) * Ambiance, Radiance: properly theme disabled and hovered accelerators (LP: #1795895) -- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- 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-themes package in Ubuntu: Fix Released 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. Regression Potential Color for elements other than the label of suggested actions is wrong 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/+source/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 1795895] Re: Accelerators on selected menu-items are not readable
This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1 --- ubuntu-themes (16.10+18.10.20181005-0ubuntu1) cosmic; urgency=medium [ Khurshid Alam ] * Remove nonexistent gnome-builder.css (LP: #1773045) [ Marco Trevisan (Treviño) ] * Radiance: fix typo in assets link for focused buttons (LP: #1781736) * Radiance: Use scaled image for buttons border (LP: #1781736) * Ambiance, Radiance: don't use padding on window buttons for chromium (LP: #1782038) * Ambiance: use default foreground color for toolbar menus (LP: #1758841) * Ambiance, Radiance: show proper arrow in combobox (LP: #1743373) * Ambiance, Radiance: use default disabled color for actions headerbar buttons (LP: #1785699) * Ambiace, Radiance: use headerbar destructive-action definition for buttons * Ambiance, Radiance: fix list selected color for gnome-boxes (LP: #1761684) * Ambiance, Radiance: properly theme disabled and hovered accelerators (LP: #1795895) -- Marco Trevisan (Treviño) Fri, 05 Oct 2018 00:13:07 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- 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/1795895 Title: Accelerators on selected menu-items are not readable Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: [ Impact ] As visible in the attached screenshot in the nautilus context menu, the accelerator is not readable when the item is selected: https://i.imgur.com/xabntIH.png [ Test case ] 1. Open Nautilus 2. Right-click on the files view 3. Select an item with an accelerator 4. The accelerator should be visible (white in Ambiance theme) [ Possible regressions ] Accelerators on menuitems on menubars might always be painted as when hovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1793092] Re: [FFe] openssl 1.1.1
systemd has "+ * Add conflicts with upstart and systemd-shim. (LP: #1793092)", but it's not straightforward to me what is going on here. Could you explain a bit more please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1793092 Title: [FFe] openssl 1.1.1 Status in openssl package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Fix Released Bug description: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Resulting in the following changes in Ubuntu: - openssl moves from 1.1.0 series to 1.1.1 LTS series - TLS1.3 is enabled, and used by default, when possible. Major feature. - All existing delta, and minimally accepted key sizes, and minimally accepted protocol versions remain the same. Proposed package is in https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of all the reverse dependencies. It demonstrates that openssl compiled as above is more compatible and has less issues than debian config. There are a few FTBFS, which are also present in cosmic-release; there are some test-suite expectations mismatch (connectivity succeeds with tls1.3 even though lower/different algos are expected); there are very little connectivity tests thus connectivity interop are the biggest issues which will be unavoidable with introducing 1.3. === Ubuntu delta summary versus debian unstable in this merge: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Further decrease security level from 1 to 0, for compatibility with openssl 1.0.2. These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/bionic/cosmic releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
** Description changed: - This means that software installed via snap isn't transparently + [Impact] + + * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. - Specifically, this is evident by e.g. $ systemd-run env. Or any other - daemons that spawn shell scripts (e.g. cloud-init metadata acquired - shell hooks, etc.). - - Since v232 systemd provides support for environment generators, snapd - should package/ship a snippet that injects the correct snapd path into - systemd environment. - - E.g.: - - $ sudo mkdir -p /usr/lib/systemd/system-environment-generators - $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ - sudo tee /usr/lib/systemd/system-environment-generators/90-snapd - - Something similar can be done for user-environment-generators too. Note - that user-environment-generators can generate unique variables per user. - - Note please use /usr/lib path, as it appears that /lib/systemd path is - not working atm. Will check if that needs to be fixed up. - - systemd in xenial does not support system-environment-generators, thus - we probably need to upload a patch to change the DEFAULT_PATH compiled - in default there. + * When a generator started to be provided by systemd, it was recognized + that $PATH is not correctly set, nonetheless, due to an environment bug + that systemd generators run in. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin + + Output should contain a complete and a valid PATH, i.e. + PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. + + [Regression Potential] + + * snapd generator was already fixed separately to cause no harm, when + running under a broken systemd. With the corrected environment, + generators will now run with a correct PATH out of the box. A slight + change of PATH will be observed by all generators, when running in + containers/initramfs-less boots. However most generators will not be + affected as they typically do not execute external binaries. -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: In Progress Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
** Description changed: + [Impact] + + * cryptsetup in bionic supports creating luks volumes with a non- + standard sector-size option, and thus this option also needs to be used + when activating the LUKS volumes. Add sector-size= option support to + /etc/crypttab. + + [Test Case] + + * Create a plain LUKS volume with sector-size 4096 + * Specify sector-size=4096 option in /etc/crypttab + * reload systemd, start systemd-cryptsetup@.service for that volume + * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) + + [Regression Potential] + + * This is an optional argument, not used by default. Currently custom + sector-size crypttab does not work correctly, and thus cannot regress. + + [Other Info] + + * Original bug report + Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode - The proposed enhancements are posted on github, see - https://github.com/systemd/systemd/issues/8881 + The proposed enhancements are posted on github, see + https://github.com/systemd/systemd/issues/8881 -- 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/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: New Status in systemd source package in Bionic: In Progress Bug description: [Impact] * cryptsetup in bionic supports creating luks volumes with a non- standard sector-size option, and thus this option also needs to be used when activating the LUKS volumes. Add sector-size= option support to /etc/crypttab. [Test Case] * Create a plain LUKS volume with sector-size 4096 * Specify sector-size=4096 option in /etc/crypttab * reload systemd, start systemd-cryptsetup@.service for that volume * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) [Regression Potential] * This is an optional argument, not used by default. Currently custom sector-size crypttab does not work correctly, and thus cannot regress. [Other Info] * Original bug report Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
** Description changed: + [Impact] + + * systemd aborts journald, upon watchdog expiry and generates lots of crash reports + * it appears that journald is simply stuck in fsync + * it has been agreed to disable watchdog timer on journald + + [Test Case] + + * watch drop-off of errors w.r.t. watchdog timer + + [Regression Potential] + + * Potentially journald does get stuck, and thus is no longer + automatically restarted with a sigabrt crash. However, so far, it is not + known to do that. + + + [Other Info] + + * Original bug report + The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. -- 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1773859] Re: upgrades to 18.04 fail
** Description changed: + [Impact] + + * Some systems fail to upgrade due to conflicts between systemd and the + (now removed from the archive) systemd-shim / upstart. + + * Instead of trying to work out what's the problem in ordering / + removal of diverts, ensure that systemd is never unpacked whilst + systemd-shim/upstart are still on disk. Thus declare conflicts against + systemd-shim/upstart packages in systemd package. + + [Test Case] + + * monitor drop-off of upgrades with below reported problem + + * Check that it is possible to upgrade to bionic's libpam-systemd from + xenial with systemd-shim installed on xenial. + + [Regression Potential] + + * systemd-shim/upstart are both removed and not supported in bionic, + thus forcing their removal via conflicts should bring the system into an + expected state. + + [Other Info] + + * original bug report + + $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: - systemd-shim + systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with - different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed + different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): - subprocess installed post-removal script returned error exit status 2 + subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: - systemd-shim + systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Committed Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Committed Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E:
[Touch-packages] [Bug 1791345] Re: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 134
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shared-mime-info (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1791345 Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 134 Status in shared-mime-info package in Ubuntu: Confirmed Bug description: It does not updates my system.Shows some type of error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shared-mime-info 1.9-2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Sep 7 22:42:12 2018 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 134 InstallationDate: Installed on 2018-08-12 (26 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 134 UpgradeStatus: Upgraded to bionic on 2018-08-25 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1791345/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
** Changed in: packagekit (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Triaged Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Triaged Status in plasma-discover source package in Bionic: Confirmed Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
Taking into account the two proposed patches, and what I believe the code to be doing, attached is a patch I believe is suitable for inclusion. ** Patch added: "0005-lp1368411.patch" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411/+attachment/5198539/+files/0005-lp1368411.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: New Status in ufw package in Ubuntu: Confirmed Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
As LP: #1790613 pakagekit remains unfixed, this update crashes the
packagekit daemon mid way through installing updates on Kubuntu.
Discover/Updater uses packagekit.
This will leave large numbers of Kubuntu users with a broken upgrade,
requiring command line fixing with 'dpkg --configure -a' before any more
updates or packages (using either apt directly or packagekit) can
installed or seen to be available.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Bionic:
Fix Committed
Bug description:
[Impact]
pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache). Also, cancalled
transactions crash as well, even if you're lucky with your apt cache, as the
"matcher" object is deleted twice.
There are two reasons: A duplicate delete statement in providesCodec
entered when cancelling the lookup, and a invalid pointer dereference
in there.
[Test case]
The daemon should not crash as below, but should print a useful message.
$ lxc launch -e ubuntu:bionic bbb
$ lxc exec bbb apt update
$ lxc exec bbb -- apt -y install packagekit
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
[...] The daemon crashed mid-transaction!
(empty lxd container seems to be able to reproduce easily)
This only tests the pointer dereference, I don't have a test for the
duplicate. But the code is obviously correct:
for ... [
if (m_cancel) {
// here used to be "delete matcher" - that's deleted
break;
}
}
delete matcher;
That is, matcher is always deleted once now, and was always deleted
twice when cancelling before.
[Regression potential]
I don't think it's possible to have a regression here, given the nature of
the fix, but if there were one, we'd see different behavior in codec lookup.
For the duplicate delete on cancelled transactions, you'd be looking
at memory leaks if there were a regression.
[Other info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.10-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2
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 and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
Bug report on previous post release update. https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1766932 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Triaged Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Triaged Status in plasma-discover source package in Bionic: Confirmed Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
On 07/09/18 11:11, Julian Andres Klode wrote: > PackageKit is not normally used for upgrading, > only for installing and removing packages. Kubuntu updated/Discover with crashing packagekit daemon testing update for LP: #1790671 ** Attachment added: "Kubunt updater crashing" https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+attachment/5198538/+files/hgsN9PE.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Triaged Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Triaged Status in plasma-discover source package in Bionic: Confirmed Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plasma-discover (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Triaged Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Triaged Status in plasma-discover source package in Bionic: Confirmed Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plasma-discover (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Triaged Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Triaged Status in plasma-discover source package in Bionic: Confirmed Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1766932] Re: packagekit daemon crashed from Discover. Requires a manual 'dpkg --configure -a' to correct.
*** This bug is a duplicate of bug 1790613 *** https://bugs.launchpad.net/bugs/1790613 ** This bug has been marked a duplicate of bug 1790613 Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1766932 Title: packagekit daemon crashed from Discover. Requires a manual 'dpkg --configure -a' to correct. Status in packagekit package in Ubuntu: Confirmed Bug description: The packagekit package has just been updated by discover (Kubuntu) from 1.1.7-1 to 1.1.7-1ubuntu0.1. Discover reported that the packagekit daemon had crashed. The resulting dpkg status is: [parent]: dpkg-query -l 'packagekit*' 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 +++-==---= iF packagekit 1.1.7-1ubunt amd64Provides a package management ser un packagekit-bac (no description available) un packagekit-bac (no description available) un packagekit-bac (no description available) un packagekit-off (no description available) un packagekit-plu (no description available) iU packagekit-too 1.1.7-1ubunt amd64Provides PackageKit command-line and apt-get upgrade reports: root@parent:~# apt-get upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. Running that command does tidy things up, but the daemon should not crash. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: packagekit 1.1.7-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 25 17:47:49 2018 InstallationDate: Installed on 2017-11-19 (157 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: packagekit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1766932/+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 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Before: packagekit (1.1.9-1ubuntu2.18.04.1)
jak@jak-t480s:~:master$ lxc exec bbb pkcon what-provides
"gstreamer1.0(decoder-audio/ac3)"
Getting provides [=]
Loading cache [=]
Querying [ ] (0%) The daemon
crashed mid-transaction!
After Unpacking packagekit-tools (1.1.9-1ubuntu2.18.04.2) over
(1.1.9-1ubuntu2.18.04.1) ...:
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
Getting provides [=]
Loading cache [=]
Querying [=]
Finished [=]
Available gstreamer1.0-plugins-good-1.14.1-1ubuntu1~ubuntu18.04.1.amd64
(ubuntu-bionic-updates-main) GStreamer plugins from the "good" set
Available gstreamer1.0-plugins-ugly-1.14.1-1~ubuntu18.04.1.amd64
(ubuntu-bionic-updates-universe) GStreamer plugins from the "ugly" set
Looks good!
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Bionic:
Fix Committed
Bug description:
[Impact]
pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache). Also, cancalled
transactions crash as well, even if you're lucky with your apt cache, as the
"matcher" object is deleted twice.
There are two reasons: A duplicate delete statement in providesCodec
entered when cancelling the lookup, and a invalid pointer dereference
in there.
[Test case]
The daemon should not crash as below, but should print a useful message.
$ lxc launch -e ubuntu:bionic bbb
$ lxc exec bbb apt update
$ lxc exec bbb -- apt -y install packagekit
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
[...] The daemon crashed mid-transaction!
(empty lxd container seems to be able to reproduce easily)
This only tests the pointer dereference, I don't have a test for the
duplicate. But the code is obviously correct:
for ... [
if (m_cancel) {
// here used to be "delete matcher" - that's deleted
break;
}
}
delete matcher;
That is, matcher is always deleted once now, and was always deleted
twice when cancelling before.
[Regression potential]
I don't think it's possible to have a regression here, given the nature of
the fix, but if there were one, we'd see different behavior in codec lookup.
For the duplicate delete on cancelled transactions, you'd be looking
at memory leaks if there were a regression.
[Other info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.10-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2
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 and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+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 1784363] Re: High delay when booting (grub waits with a blank purple screen for 10 seconds before booting the kernel)
** No longer affects: ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1784363 Title: High delay when booting (grub waits with a blank purple screen for 10 seconds before booting the kernel) Status in grub2 package in Ubuntu: Triaged Bug description: Steps to reproduce -- 1. Upgrade `grub-pc` to 2.02-2ubuntu8.2 (installed by default on 18.04.1?) 2. Reboot Expected behavior - Timeout is set to 3-5 seconds (as I remember) Actual behavior --- Boot delayed - timeout is set to 15 seconds (as counted) External information vitalkanev@:~$ lsb_release -rd && echo && LANG=C apt policy grub-pc && echo && uname -a Description: Ubuntu 18.04.1 LTS Release: 18.04 grub-pc: Installed: 2.02-2ubuntu8.2 Candidate: 2.02-2ubuntu8.2 Version table: *** 2.02-2ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.02-2ubuntu8 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Linux 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: grub-pc 2.02-2ubuntu8.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 CurrentDesktop: XFCE Date: Mon Jul 30 14:00:47 2018 InstallationDate: Installed on 2018-07-15 (14 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1784363/+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 1620054] Re: Google reCaptcha does not work in browser
*** This bug is a duplicate of bug 1599146 *** https://bugs.launchpad.net/bugs/1599146 yes, I m also facing this Google reCaptcha issue, How can I solved this issue. click here https://www.outlooktechnicalsupportnumbers.com/ if anyone faces an outlook issue. ** Attachment added: "out.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+attachment/5198514/+files/out.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1620054 Title: Google reCaptcha does not work in browser Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I was not able to post a reply on xda developers forum. Recaptcha told me that the browser does not support the widget. It seemed strange since this is a commonly used captcha framework. However, testing with the following test page https://patrickhlauke.github.io/recaptcha/ revealed that reCaptcha is not working at ll in the Ubuntu Browser. Since this is an important verification method these days I would assume someone needs to talk to Google to either allow our User-Agent, or we must fake once again the UA string in some way. This is really a bad thing I know. But what does it help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+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
