[Touch-packages] [Bug 1681652] [NEW] Laptop screen does not turn off when closing lid from login screen.
Public bug reported: I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414. I only changed in Power Settings: When plugged in > When lid is close = Do Nothing Brightness & Lock Settings were not changed; Lock Screen after: Screen turns off If I close the laptop lid while logged in at the Unity Desktop, the screen will fade to black and turn off, which I think is normal and expected. Then when I open the lid I get the login screen, which I also expect. Now, if I don't login and just close the lid, the screen does not fade to black nor turn off. I would expect the screen to fade to black and turn off also from the login screen. This appears to be a small issue, at least on my system. If anyone needs specific information about the system, please ask. ** Affects: systemd (Ubuntu) Importance: Undecided Status: 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/1681652 Title: Laptop screen does not turn off when closing lid from login screen. Status in systemd package in Ubuntu: New Bug description: I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414. I only changed in Power Settings: When plugged in > When lid is close = Do Nothing Brightness & Lock Settings were not changed; Lock Screen after: Screen turns off If I close the laptop lid while logged in at the Unity Desktop, the screen will fade to black and turn off, which I think is normal and expected. Then when I open the lid I get the login screen, which I also expect. Now, if I don't login and just close the lid, the screen does not fade to black nor turn off. I would expect the screen to fade to black and turn off also from the login screen. This appears to be a small issue, at least on my system. If anyone needs specific information about the system, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681652/+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 1663794] Re: Poweroff/Reboot Hangs :: Ubuntu 16.04
Then the best way is to file a bug at https://bugzilla.kernel.org . -- 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/1663794 Title: Poweroff/Reboot Hangs :: Ubuntu 16.04 Status in systemd package in Ubuntu: New Bug description: After upgrading my laptop (Dell Inspiron 5447) to Ubuntu 16.04 I saw that I can not shut down or restart after a few hours using the system. It hangs in Plymouth and stays that way until I force the shutdown by pressing the On / Off button. As this is a common bug (there are tons of questions on the Internet) I tried to fix it, but none of my attempts were effective. Already tried: 1. Boot with acpi=force, acpi=noirq and pci=noacpi 2. Disable Swap 3. Run 'sync' before reboot or shutdown 4. Use another kernel version (4.7, 4.8, 4.9 and 4.10 from mainline) 5. Disabling USB 3.0 6. Disabling TLP The most interesting thing is: I can shutdown/reboot normally using 14.04 and the kernel from Xenial HWE and it's because of that I believe this is a systemd bug. The problem can also be reached just running "halt" of "systemctl halt" after booting 16.04 in this machine. Running these commands with "force" option is working fine. My Machine Specs: Dell Inspiron 5447 - BIOS A10 Intel Core i5-4210 Processor 8 GB RAM 480 SSD Sandisk Hybrid Graphics (i915/amdgpu - Radeon R7 M265) --- BUG Information Reproducible: Always Steps to Reproduce: 1.Power on the machine 2.Do something, anything or nothing for a few hours 3.Try to shutdown/reboot using halt, shutdown, reboot, etc Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off/rebooting the machine. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-10 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5447 Package: systemd 229-4ubuntu16 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic root=UUID=d725c86b-f9f7-4ae9-8cd8-7c27f3a8a06a ro quiet xhci_hcd.quirks=270336 splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0MHP6R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5447 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2017-02-11T01:12:03.22 mtime.conffile..etc.systemd.system.conf: 2017-02-09T22:18:49.885303 mtime.conffile..etc.systemd.timesyncd.conf: 2017-02-09T22:19:05.646455 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1663794/+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 1662632] Re: Installing 0.26.1 breaks calendar app (and others)
[Expired for qtubuntu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qtubuntu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1662632 Title: Installing 0.26.1 breaks calendar app (and others) Status in Mir: Expired Status in qtubuntu package in Ubuntu: Expired Bug description: When installing the 0.26.1 silo I can no longer run calendar on Unity8. It gives this error in the logs: Feb 07 10:30:31 seven kernel: QSGRenderThread[6690]: segfault at 30 ip 7f9fa93fcdc8 sp 7f9f655c6b28 error 4 in libEGL.so.1.0.0[7f9fa93e2000+3] Xenial+Overlay Deb based Unity8 Snaps: ubuntu-app-platform 1 33 canonical devmode ubuntu-calendar-app 0.1.1 23 canonical devmode To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1662632/+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 1662632] Re: Installing 0.26.1 breaks calendar app (and others)
[Expired for Mir because there has been no activity for 60 days.] ** Changed in: mir Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1662632 Title: Installing 0.26.1 breaks calendar app (and others) Status in Mir: Expired Status in qtubuntu package in Ubuntu: Expired Bug description: When installing the 0.26.1 silo I can no longer run calendar on Unity8. It gives this error in the logs: Feb 07 10:30:31 seven kernel: QSGRenderThread[6690]: segfault at 30 ip 7f9fa93fcdc8 sp 7f9f655c6b28 error 4 in libEGL.so.1.0.0[7f9fa93e2000+3] Xenial+Overlay Deb based Unity8 Snaps: ubuntu-app-platform 1 33 canonical devmode ubuntu-calendar-app 0.1.1 23 canonical devmode To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1662632/+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 1663256] Re: cannot login to unity 8 - mouse and loading starting screen freeze
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1663256 Title: cannot login to unity 8 - mouse and loading starting screen freeze Status in unity8 package in Ubuntu: Expired Bug description: When I log into unity 8 session first i see black screen and next is wallpeper with left and top dash and loading starting scope with apps but no apps show up just freezes everything. Mouse and keyboard is not working. When I log in to unity 7 everthing is fine. Where is the problem? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170131.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 9 15:52:20 2017 InstallationDate: Installed on 2017-01-28 (12 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2017-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1663256/+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 1681616] Re: lightdm crashed with SIGSEGV
*** This bug is a duplicate of bug 1675141 *** https://bugs.launchpad.net/bugs/1675141 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1675141, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1681616/+attachment/4859947/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1681616/+attachment/4859949/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1681616/+attachment/4859955/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1681616/+attachment/4859956/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1681616/+attachment/4859957/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1681616/+attachment/4859958/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1681616/+attachment/4859959/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1675141 lightdm crashed with SIGSEGV in munmap() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1681616 Title: lightdm crashed with SIGSEGV Status in lightdm package in Ubuntu: New Bug description: I just got this segfault after pressing Ctrl-Alt-F1 and switching to single user mode with "init 1". ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2 Uname: Linux 4.11.0-041100rc5-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Mon Apr 10 22:25:34 2017 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2015-11-23 (504 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmConfig: [Seat:*] autologin-guest=false autologin-user=teste autologin-user-timeout=0 ProcCmdline: lightdm --session-child 13 16 ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fbee2958f29:mov0x8(%rax),%r12 PC (0x7fbee2958f29) ok source "0x8(%rax)" (0x7fbee2b42a40) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () from /lib64/ld-linux-x86-64.so.2 ?? () from /lib64/ld-linux-x86-64.so.2 ?? () from /lib64/ld-linux-x86-64.so.2 ?? () from /lib64/ld-linux-x86-64.so.2 ?? () from /lib64/ld-linux-x86-64.so.2 Title: lightdm crashed with SIGSEGV UpgradeStatus: Upgraded to zesty on 2017-03-25 (16 days ago) UserGroups: upstart.lightdm.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1681616/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
I'm not sure but it sounds like Alberto's branch might fix this bug for the general case. However we would need a new Mir running under Unity8 (or a backported fix) to confirm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
I'm not sure but it sounds like Alberto's branch might fix this bug for the general case. However we would need a new Mir running under Unity8 (or a backported fix) to confirm. ** Changed in: mir Assignee: (unassigned) => Alberto Aguirre (albaguirre) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1668465] Re: weird color display after suspend.
I found the same bug. This is my graphic card (but I'm not sure how to check the driver version): Video Card: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) OS version: Ubuntu 16.04.2 LTS I think that those "funny" colors space is the video card memory that wasn't refreshed. Maybe during the suspend it got some noise values and it should be fixed with a 'redraw' call. But I'm no expert on Ubuntu or video card code :P -- 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/1668465 Title: weird color display after suspend. Status in lightdm package in Ubuntu: Confirmed Bug description: I restart the display manager then the display is fine again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 28 09:24:44 2017 InstallationDate: Installed on 2016-03-31 (334 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-10-19 (131 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1668465/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt
This bug was fixed in the package software-properties - 0.96.24.13 --- software-properties (0.96.24.13) zesty; urgency=medium * software-properties-gtk: also fix the backend code to set the gnome debconf frontend, without which libgtk2-perl goes unused. -- Steve Langasek Mon, 10 Apr 2017 14:25:17 -0700 ** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt Status in shim-signed package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Fix Released Bug description: I've encountered this repeatedly. In the first installation -- on updating via Software Updater, this crashed on upgrading the shim-signed package. On suggestions from here: I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work, however when I now try to swap the display driver, from xorg --> nvidia. This now triggered the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 18:21:32 2017 DuplicateSignature: package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ... Running in non-interactive mode, doing nothing. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shim-signed Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+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 1681596] Re: UpgradeStatus only checks for ubuntu-release-upgrader upgrades
** Tags added: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1681596 Title: UpgradeStatus only checks for ubuntu-release-upgrader upgrades Status in apport package in Ubuntu: Triaged Bug description: In add_release_info of the generic ubuntu apport hook we can see the following: log = '/var/log/dist-upgrade/main.log' if os.path.exists(log): mtime = os.stat(log).st_mtime human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime)) delta = time.time() - mtime # Would be nice if this also showed which release was originally installed report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' % (release_codename, human_mtime, delta / 86400) else: report['UpgradeStatus'] = 'No upgrade log present (probably fresh install)' UpgradeStatus doesn't take into consideration the possibility that people upgraded by editing their sources.list file and ran 'apt-get dist-upgrade', so saying it is "probably a fresh install" is wrong. Apport can up creating reports with a InstallationMedia of Precise, DistroRelease of Yakkety, but then a UpgradeStatus of "No upgrade log present..." which is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681596/+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 1681596] [NEW] UpgradeStatus only checks for ubuntu-release-upgrader upgrades
Public bug reported: In add_release_info of the generic ubuntu apport hook we can see the following: log = '/var/log/dist-upgrade/main.log' if os.path.exists(log): mtime = os.stat(log).st_mtime human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime)) delta = time.time() - mtime # Would be nice if this also showed which release was originally installed report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' % (release_codename, human_mtime, delta / 86400) else: report['UpgradeStatus'] = 'No upgrade log present (probably fresh install)' UpgradeStatus doesn't take into consideration the possibility that people upgraded by editing their sources.list file and ran 'apt-get dist-upgrade', so saying it is "probably a fresh install" is wrong. Apport can up creating reports with a InstallationMedia of Precise, DistroRelease of Yakkety, but then a UpgradeStatus of "No upgrade log present..." which is wrong. ** Affects: apport (Ubuntu) Importance: Medium Status: Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1681596 Title: UpgradeStatus only checks for ubuntu-release-upgrader upgrades Status in apport package in Ubuntu: Triaged Bug description: In add_release_info of the generic ubuntu apport hook we can see the following: log = '/var/log/dist-upgrade/main.log' if os.path.exists(log): mtime = os.stat(log).st_mtime human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime)) delta = time.time() - mtime # Would be nice if this also showed which release was originally installed report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' % (release_codename, human_mtime, delta / 86400) else: report['UpgradeStatus'] = 'No upgrade log present (probably fresh install)' UpgradeStatus doesn't take into consideration the possibility that people upgraded by editing their sources.list file and ran 'apt-get dist-upgrade', so saying it is "probably a fresh install" is wrong. Apport can up creating reports with a InstallationMedia of Precise, DistroRelease of Yakkety, but then a UpgradeStatus of "No upgrade log present..." which is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681596/+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 1681597] [NEW] DNS broken after >50m of uptime
Public bug reported: After about 50m of uptime news.ycombinator.com stops working in Chromium: news.ycombinator.com’s server's DNS address could not be found. DNS_PROBE_FINISHED_NXDOMAIN $ host news.ycombinator.com Host news.ycombinator.com not found: 2(SERVFAIL) This is a *regression* from Ubuntu 16.10, where DNS worked flawlessly. Workarounds: * 'systemctl restart systemd-resolved' solves the problem for another 50m * disable systemd-resolved and use the DNS server directly. This involves removing 'resolve [!UNAVAIL=return]' from nsswitch.conf, and disabling the systemd-resolved unit Logs show DNSSEC related errors, and DNSSEC getting disabled and reenabled: -- Logs begin at Mon 2017-04-10 23:10:59 BST, end at Tue 2017-04-11 00:11:14 BST. -- Apr 10 23:11:01 bolt systemd[1]: Starting Network Name Resolution... Apr 10 23:11:01 bolt systemd-resolved[1351]: Positive Trust Anchors: Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 10 23:11:01 bolt systemd-resolved[1351]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Apr 10 23:11:01 bolt systemd-resolved[1351]: Using system hostname 'bolt'. Apr 10 23:11:01 bolt systemd[1]: Started Network Name Resolution. Apr 10 23:11:05 bolt systemd-resolved[1351]: Switching to DNS server 194.168.4.100 for interface wlp3s0. Apr 10 23:11:06 bolt systemd-resolved[1351]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.4.100. Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question com IN SOA: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question ubuntu.com IN DS: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question ubuntu.com IN SOA: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN DS: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN A: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: Server 194.168.4.100 does not support DNSSEC, downgrading to non-DNSSEC mode. Apr 10 23:11:06 bolt systemd-resolved[1351]: Switching to DNS server 194.168.8.100 for interface wlp3s0. Apr 10 23:11:07 bolt systemd-resolved[1351]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.8.100. Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question clamav.net IN DS: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question clamav.net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question cvd.clamav.net IN DS: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question cvd.clamav.net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN DS: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN TXT: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: Server 194.168.8.100 does not support DNSSEC, downgrading to non-DNSSEC mode. Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN A: failed-auxiliary Apr 10 23:11:52 bolt systemd[1]: Stopping Network Name Resolution... Apr 10 23:11:52 bolt systemd[1]: Stopped Network Name Resolution. Apr 10 23:11:52 bolt systemd[1]: Starting Network Name Resolution... Apr 10 23:11:52 bolt systemd-resolved[2868]: Positive Trust Anchors: Apr 10 23:11:52 bolt systemd-resolved[2868]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Apr 10 23:11:52 bolt systemd-resolved[2868]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 10 23
[Touch-packages] [Bug 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt
I believe the problem is that nothing ensures that the desktop components which select and install software have access to a GUI debconf frontend. I think the proper solution is for each of the frontends to aptdaemon to depend/recommend a suitable debconf frontend component (libgtk2-perl, libqtgui4-perl/libqtcore4-perl). For 17.04, this includes at least gnome-software and software- properties-gtk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt Status in shim-signed package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Triaged Bug description: I've encountered this repeatedly. In the first installation -- on updating via Software Updater, this crashed on upgrading the shim-signed package. On suggestions from here: I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work, however when I now try to swap the display driver, from xorg --> nvidia. This now triggered the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 18:21:32 2017 DuplicateSignature: package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ... Running in non-interactive mode, doing nothing. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shim-signed Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt
** Branch linked: lp:software-properties -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt Status in shim-signed package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Triaged Bug description: I've encountered this repeatedly. In the first installation -- on updating via Software Updater, this crashed on upgrading the shim-signed package. On suggestions from here: I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work, however when I now try to swap the display driver, from xorg --> nvidia. This now triggered the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 18:21:32 2017 DuplicateSignature: package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ... Running in non-interactive mode, doing nothing. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shim-signed Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
Fix committed into lp:mir at revision 4150, scheduled for release in mir, milestone 0.28.0 ** Changed in: mir Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu) Importance: Undecided => Critical ** Changed in: shim-signed (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt Status in shim-signed package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Triaged Bug description: I've encountered this repeatedly. In the first installation -- on updating via Software Updater, this crashed on upgrading the shim-signed package. On suggestions from here: I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work, however when I now try to swap the display driver, from xorg --> nvidia. This now triggered the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 18:21:32 2017 DuplicateSignature: package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ... Running in non-interactive mode, doing nothing. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shim-signed Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+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 1681255] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1681255 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It appears every time I start the OS. Installed using daily build of the 8th April 2017. OS: Ubuntu 17.04 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Sun Apr 9 20:11:45 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2017-04-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: LANG=es_ES.UTF-8 LANGUAGE=es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681255/+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 1681552] Re: libtiff5; Internal error, unknown tag
Minimal code and sample image to reproduce error. ** Attachment added: "Minimal code and sample image to reproduce error" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1681552/+attachment/4859864/+files/test.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1681552 Title: libtiff5; Internal error, unknown tag Status in tiff package in Ubuntu: New Bug description: When calling libtiff5 through libfreeimage3 on a fresh (~month old) install of xenial. No tiff tags are recognized from the defined list in tiff.h (installed with libtiff5-dev) from the EXIF section. Each call to load a tiff results in the following non fatal errors being reported. TIFFFieldWithTag: Internal error, unknown tag 0x829a. TIFFFieldWithTag: Internal error, unknown tag 0x829d. TIFFFieldWithTag: Internal error, unknown tag 0x8822. TIFFFieldWithTag: Internal error, unknown tag 0x8824. TIFFFieldWithTag: Internal error, unknown tag 0x8827. TIFFFieldWithTag: Internal error, unknown tag 0x8828. TIFFFieldWithTag: Internal error, unknown tag 0x9000. TIFFFieldWithTag: Internal error, unknown tag 0x9003. TIFFFieldWithTag: Internal error, unknown tag 0x9004. TIFFFieldWithTag: Internal error, unknown tag 0x9101. TIFFFieldWithTag: Internal error, unknown tag 0x9102. TIFFFieldWithTag: Internal error, unknown tag 0x9201. TIFFFieldWithTag: Internal error, unknown tag 0x9202. TIFFFieldWithTag: Internal error, unknown tag 0x9203. TIFFFieldWithTag: Internal error, unknown tag 0x9204. TIFFFieldWithTag: Internal error, unknown tag 0x9205. TIFFFieldWithTag: Internal error, unknown tag 0x9206. TIFFFieldWithTag: Internal error, unknown tag 0x9207. TIFFFieldWithTag: Internal error, unknown tag 0x9208. TIFFFieldWithTag: Internal error, unknown tag 0x9209. TIFFFieldWithTag: Internal error, unknown tag 0x920a. TIFFFieldWithTag: Internal error, unknown tag 0x9214. TIFFFieldWithTag: Internal error, unknown tag 0x927c. TIFFFieldWithTag: Internal error, unknown tag 0x9286. TIFFFieldWithTag: Internal error, unknown tag 0x9290. TIFFFieldWithTag: Internal error, unknown tag 0x9291. TIFFFieldWithTag: Internal error, unknown tag 0x9292. TIFFFieldWithTag: Internal error, unknown tag 0xa000. TIFFFieldWithTag: Internal error, unknown tag 0xa001. TIFFFieldWithTag: Internal error, unknown tag 0xa002. TIFFFieldWithTag: Internal error, unknown tag 0xa003. TIFFFieldWithTag: Internal error, unknown tag 0xa004. TIFFFieldWithTag: Internal error, unknown tag 0xa20b. TIFFFieldWithTag: Internal error, unknown tag 0xa20c. TIFFFieldWithTag: Internal error, unknown tag 0xa20e. TIFFFieldWithTag: Internal error, unknown tag 0xa20f. TIFFFieldWithTag: Internal error, unknown tag 0xa210. TIFFFieldWithTag: Internal error, unknown tag 0xa214. TIFFFieldWithTag: Internal error, unknown tag 0xa215. TIFFFieldWithTag: Internal error, unknown tag 0xa217. TIFFFieldWithTag: Internal error, unknown tag 0xa300. TIFFFieldWithTag: Internal error, unknown tag 0xa301. TIFFFieldWithTag: Internal error, unknown tag 0xa302. TIFFFieldWithTag: Internal error, unknown tag 0xa401. TIFFFieldWithTag: Internal error, unknown tag 0xa402. TIFFFieldWithTag: Internal error, unknown tag 0xa403. TIFFFieldWithTag: Internal error, unknown tag 0xa404. TIFFFieldWithTag: Internal error, unknown tag 0xa405. TIFFFieldWithTag: Internal error, unknown tag 0xa406. TIFFFieldWithTag: Internal error, unknown tag 0xa407. TIFFFieldWithTag: Internal error, unknown tag 0xa408. TIFFFieldWithTag: Internal error, unknown tag 0xa409. TIFFFieldWithTag: Internal error, unknown tag 0xa40a. TIFFFieldWithTag: Internal error, unknown tag 0xa40b. TIFFFieldWithTag: Internal error, unknown tag 0xa40c. TIFFFieldWithTag: Internal error, unknown tag 0xa407. TIFFFieldWithTag: Internal error, unknown tag 0xa407. TIFFFieldWithTag: Internal error, unknown tag 0xa420. lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy libtiff5 libtiff5: Installed: 4.0.6-1ubuntu0.1 Candidate: 4.0.6-1ubuntu0.1 Version table: *** 4.0.6-1ubuntu0.1 500 500 http://us.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 4.0.6-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1681552/+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 1599601] Re: courier-authdaemon not enabled by default to start
Deeply sorry for the wrong assignment. Anyway the description reported the actual package. Regards ** Package changed: xorg (Ubuntu) => courier-authlib (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/1599601 Title: courier-authdaemon not enabled by default to start Status in courier-authlib package in Ubuntu: Confirmed Bug description: The service authdaemond is not started by default at startup. I had to use the following command so the service was started at startup : $> sudo systemctl enable courier-authdaemon.service Then the courier-imap with no particular authentification (ie through authdaemon) method was able to work perfectly! To give more details, the error encountered was that I wasn't able to use the imap over ssl (although it worked perfectly up to 15.10 with nothing special to do) In /var/log/syslog, the logged lines that appeared each time my mail client was trying to access to the local imap server were: imapd-ssl: authdaemon: s_connect() failed: No such file or directory imapd-ssl: LOGIN FAILED, user=JR, ip=[:::192.168.1.254] imapd-ssl: authentication error: No such file or directory The release is: Description:Ubuntu 16.04 LTS Release:16.04 courier-authdaemon: Installé : 0.66.4-3build1 Candidat : 0.66.4-3build1 Table de version : *** 0.66.4-3build1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status I expected that the service was started automatically at startup. What happened instead was it was not enabled, leading to this mess on my kubuntu installation. So if the package's maintainer could check whether on a usual install( maybe this happened only on my computer) this service was enabled by default, that could help other people. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 4 20:19:02 2016 InstallationDate: Installed on 2016-05-25 (40 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/courier-authlib/+bug/1599601/+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 1681552] [NEW] libtiff5; Internal error, unknown tag
Public bug reported: When calling libtiff5 through libfreeimage3 on a fresh (~month old) install of xenial. No tiff tags are recognized from the defined list in tiff.h (installed with libtiff5-dev) from the EXIF section. Each call to load a tiff results in the following non fatal errors being reported. TIFFFieldWithTag: Internal error, unknown tag 0x829a. TIFFFieldWithTag: Internal error, unknown tag 0x829d. TIFFFieldWithTag: Internal error, unknown tag 0x8822. TIFFFieldWithTag: Internal error, unknown tag 0x8824. TIFFFieldWithTag: Internal error, unknown tag 0x8827. TIFFFieldWithTag: Internal error, unknown tag 0x8828. TIFFFieldWithTag: Internal error, unknown tag 0x9000. TIFFFieldWithTag: Internal error, unknown tag 0x9003. TIFFFieldWithTag: Internal error, unknown tag 0x9004. TIFFFieldWithTag: Internal error, unknown tag 0x9101. TIFFFieldWithTag: Internal error, unknown tag 0x9102. TIFFFieldWithTag: Internal error, unknown tag 0x9201. TIFFFieldWithTag: Internal error, unknown tag 0x9202. TIFFFieldWithTag: Internal error, unknown tag 0x9203. TIFFFieldWithTag: Internal error, unknown tag 0x9204. TIFFFieldWithTag: Internal error, unknown tag 0x9205. TIFFFieldWithTag: Internal error, unknown tag 0x9206. TIFFFieldWithTag: Internal error, unknown tag 0x9207. TIFFFieldWithTag: Internal error, unknown tag 0x9208. TIFFFieldWithTag: Internal error, unknown tag 0x9209. TIFFFieldWithTag: Internal error, unknown tag 0x920a. TIFFFieldWithTag: Internal error, unknown tag 0x9214. TIFFFieldWithTag: Internal error, unknown tag 0x927c. TIFFFieldWithTag: Internal error, unknown tag 0x9286. TIFFFieldWithTag: Internal error, unknown tag 0x9290. TIFFFieldWithTag: Internal error, unknown tag 0x9291. TIFFFieldWithTag: Internal error, unknown tag 0x9292. TIFFFieldWithTag: Internal error, unknown tag 0xa000. TIFFFieldWithTag: Internal error, unknown tag 0xa001. TIFFFieldWithTag: Internal error, unknown tag 0xa002. TIFFFieldWithTag: Internal error, unknown tag 0xa003. TIFFFieldWithTag: Internal error, unknown tag 0xa004. TIFFFieldWithTag: Internal error, unknown tag 0xa20b. TIFFFieldWithTag: Internal error, unknown tag 0xa20c. TIFFFieldWithTag: Internal error, unknown tag 0xa20e. TIFFFieldWithTag: Internal error, unknown tag 0xa20f. TIFFFieldWithTag: Internal error, unknown tag 0xa210. TIFFFieldWithTag: Internal error, unknown tag 0xa214. TIFFFieldWithTag: Internal error, unknown tag 0xa215. TIFFFieldWithTag: Internal error, unknown tag 0xa217. TIFFFieldWithTag: Internal error, unknown tag 0xa300. TIFFFieldWithTag: Internal error, unknown tag 0xa301. TIFFFieldWithTag: Internal error, unknown tag 0xa302. TIFFFieldWithTag: Internal error, unknown tag 0xa401. TIFFFieldWithTag: Internal error, unknown tag 0xa402. TIFFFieldWithTag: Internal error, unknown tag 0xa403. TIFFFieldWithTag: Internal error, unknown tag 0xa404. TIFFFieldWithTag: Internal error, unknown tag 0xa405. TIFFFieldWithTag: Internal error, unknown tag 0xa406. TIFFFieldWithTag: Internal error, unknown tag 0xa407. TIFFFieldWithTag: Internal error, unknown tag 0xa408. TIFFFieldWithTag: Internal error, unknown tag 0xa409. TIFFFieldWithTag: Internal error, unknown tag 0xa40a. TIFFFieldWithTag: Internal error, unknown tag 0xa40b. TIFFFieldWithTag: Internal error, unknown tag 0xa40c. TIFFFieldWithTag: Internal error, unknown tag 0xa407. TIFFFieldWithTag: Internal error, unknown tag 0xa407. TIFFFieldWithTag: Internal error, unknown tag 0xa420. lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy libtiff5 libtiff5: Installed: 4.0.6-1ubuntu0.1 Candidate: 4.0.6-1ubuntu0.1 Version table: *** 4.0.6-1ubuntu0.1 500 500 http://us.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 4.0.6-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Affects: tiff (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1681552 Title: libtiff5; Internal error, unknown tag Status in tiff package in Ubuntu: New Bug description: When calling libtiff5 through libfreeimage3 on a fresh (~month old) install of xenial. No tiff tags are recognized from the defined list in tiff.h (installed with libtiff5-dev) from the EXIF section. Each call to load a tiff results in the following non fatal errors being reported. TIFFFieldWithTag: Internal error, unknown tag 0x829a. TIFFFieldWithTag: Internal error, unknown tag 0x829d. TIFFFieldWithTag: Internal error, unknown tag 0x8822. TIFFFieldWithTag: Internal error, unknown tag 0x8824. TIFFFieldWithTag: Internal error, unknown tag 0x8827. TIFFFieldWithTag: Internal error, unknown tag 0x8828. TIFFFieldWithTag: Internal error, unknown tag 0x9000. TIF
[Touch-packages] [Bug 1680750] Re: pm-hibernate does nothing at all
@teo8976, thanks for reporting this. Currently there is insufficient information to even begin work on this report. If we are to track down a root cause or help your diagnose this any further then we would need to know more. I am no expert on pm-utils, but I think the following would get something going: 1. It sounds like this used to work? Was it working on 16.04 and only recently broke? 2. What model is your hardware? 3. Did you recently update the system BIOS? Are you running the latest? You can collect this by running sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date I cannot promise this will get you a resolution, but more information is indeed required. I am marking this as 'incomplete' and feel free to move it back to 'new' when you respond. ** Changed in: pm-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1680750 Title: pm-hibernate does nothing at all Status in pm-utils package in Ubuntu: Incomplete Bug description: I have run from a command line: # sudo pm-hibernate and NOTHING f***ing happens. Usually it works (except for lots of issues on resume), but now I have tried it twice and it does nothing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: powerman (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 7 10:47:47 2017 InstallationDate: Installed on 2013-10-11 (1273 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: powerman UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1680750/+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 1681255] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1681255 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: New Bug description: It appears every time I start the OS. Installed using daily build of the 8th April 2017. OS: Ubuntu 17.04 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Sun Apr 9 20:11:45 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2017-04-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: LANG=es_ES.UTF-8 LANGUAGE=es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681255/+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 1599601] Re: courier-authdaemon not enabled by default to start
what on earth does this have to do with xorg? -- 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/1599601 Title: courier-authdaemon not enabled by default to start Status in xorg package in Ubuntu: Confirmed Bug description: The service authdaemond is not started by default at startup. I had to use the following command so the service was started at startup : $> sudo systemctl enable courier-authdaemon.service Then the courier-imap with no particular authentification (ie through authdaemon) method was able to work perfectly! To give more details, the error encountered was that I wasn't able to use the imap over ssl (although it worked perfectly up to 15.10 with nothing special to do) In /var/log/syslog, the logged lines that appeared each time my mail client was trying to access to the local imap server were: imapd-ssl: authdaemon: s_connect() failed: No such file or directory imapd-ssl: LOGIN FAILED, user=JR, ip=[:::192.168.1.254] imapd-ssl: authentication error: No such file or directory The release is: Description:Ubuntu 16.04 LTS Release:16.04 courier-authdaemon: Installé : 0.66.4-3build1 Candidat : 0.66.4-3build1 Table de version : *** 0.66.4-3build1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status I expected that the service was started automatically at startup. What happened instead was it was not enabled, leading to this mess on my kubuntu installation. So if the package's maintainer could check whether on a usual install( maybe this happened only on my computer) this service was enabled by default, that could help other people. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 4 20:19:02 2016 InstallationDate: Installed on 2016-05-25 (40 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1599601/+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 1660762] Comment bridged from LTC Bugzilla
--- Comment From maur...@br.ibm.com 2017-04-10 14:51 EDT--- Hi Narasimham! I've tried to reproduce the issue with the two most recent kernels available for ubuntu 1704, and it seems fixed. I didn't spend time looking for which patch fixed it. I guess it was fixed at Linux 4.10.0-15-generic, newest 4.10.0-19-generic also works fine. Shallow explanation for this issue is: when unbinding /binding the device driver the kernel wasn't generating the events udev has to capture to take a corresponding action, thus the network configuration wasn't happening. Now it's easy to see many events during {un,/}bind: 1 - Started udev's monitor: root@redhot:~# udevadm monitor --tag-match="enP1p12s0f0" & [1] 5226 2 - Unbinded the device root@redhot:~# echo 0001:0c:00.0 > /sys/bus/pci/drivers/tg3/unbind KERNEL[555.821104] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/ptp/ptp0 (ptp) KERNEL[555.900035] remove /kernel/slab/:atA-192/cgroup/dentry(1363:ureadahead-stop.service) (cgroup) KERNEL[555.900314] remove /kernel/slab/inode_cache/cgroup/inode_cache(1363:ureadahead-stop.service) (cgroup) KERNEL[555.900459] remove /kernel/slab/:tA-256/cgroup/cred_jar(1363:ureadahead-stop.service) (cgroup) KERNEL[555.900597] remove /kernel/slab/:tA-0001408/cgroup/mm_struct(1363:ureadahead-stop.service) (cgroup) KERNEL[555.900734] remove /kernel/slab/:tA-200/cgroup/vm_area_struct(1363:ureadahead-stop.service) (cgroup) KERNEL[555.900878] remove /kernel/slab/:tA-064/cgroup/anon_vma_chain(1363:ureadahead-stop.service) (cgroup) KERNEL[555.901027] remove /kernel/slab/anon_vma/cgroup/anon_vma(1363:ureadahead-stop.service) (cgroup) KERNEL[555.901169] remove /kernel/slab/proc_inode_cache/cgroup/proc_inode_cache(1363:ureadahead-stop.service) (cgroup) KERNEL[555.901447] remove /kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(1363:ureadahead-stop.service) (cgroup) KERNEL[555.901654] remove /kernel/slab/:t-256/cgroup/kmalloc-256(1363:ureadahead-stop.service) (cgroup) KERNEL[555.901857] remove /kernel/slab/:t-512/cgroup/kmalloc-512(1363:ureadahead-stop.service) (cgroup) KERNEL[555.902004] remove /kernel/slab/:t-0001024/cgroup/kmalloc-1024(1363:ureadahead-stop.service) (cgroup) KERNEL[556.786692] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/net/enP1p12s0f0/queues/rx-3 (queues) KERNEL[556.787004] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/net/enP1p12s0f0/queues/rx-2 (queues) KERNEL[556.787452] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/net/enP1p12s0f0/queues/rx-1 (queues) KERNEL[556.787660] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/net/enP1p12s0f0/queues/rx-0 (queues) KERNEL[556.787866] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/net/enP1p12s0f0/queues/tx-0 (queues) KERNEL[556.788102] remove /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:10.0/0001:0c:00.0/net/enP1p12s0f0 (net) root@redhot:~# KERNEL[556.931045] add /kernel/slab/:atA-192/cgroup/dentry(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.931272] add /kernel/slab/inode_cache/cgroup/inode_cache(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.931523] add /kernel/slab/:tA-256/cgroup/cred_jar(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.931732] add /kernel/slab/:tA-0001408/cgroup/mm_struct(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.931985] add /kernel/slab/:tA-200/cgroup/vm_area_struct(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.932215] add /kernel/slab/:tA-064/cgroup/anon_vma_chain(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.932428] add /kernel/slab/anon_vma/cgroup/anon_vma(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.934868] add /kernel/slab/proc_inode_cache/cgroup/proc_inode_cache(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.935926] add /kernel/slab/:tA-0005632/cgroup/task_struct(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.936152] add /kernel/slab/:t-0016384/cgroup/kmalloc-16384(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.936358] add /kernel/slab/:tA-128/cgroup/pid(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.936618] add /kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.936976] add /kernel/slab/:t-256/cgroup/kmalloc-256(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.937190] add /kernel/slab/:t-512/cgroup/kmalloc-512(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.938335] add /kernel/slab/:t-0001024/cgroup/kmalloc-1024(1377:NetworkManager-dispatcher.service) (cgroup) KERNEL[556.939091] add /
[Touch-packages] [Bug 1669250] Re: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Could you please include the output of 'python --version'? Thanks in advance. ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1669250 Title: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in apport package in Ubuntu: Incomplete Bug description: anzhuangshibai ProblemType: Package DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportLog: ERROR: apport (pid 4749) Thu Mar 2 11:10:01 2017: called for pid 4737, signal 11, core limit 0 ERROR: apport (pid 4749) Thu Mar 2 11:10:01 2017: executable was modified after program start, ignoring ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashReports: 600:0:122:253095:2017-03-02 11:40:29.509586811 +0800:2017-03-02 11:40:30.509586811 +0800:/var/crash/apport.0.crash Date: Thu Mar 2 11:40:29 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-01 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: apport Title: package apport 2.20.3-0ubuntu8 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1669250/+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 1681528] Re: Include information about python versions
** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu) Milestone: None => ubuntu-17.05 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1681528 Title: Include information about python versions Status in apport package in Ubuntu: New Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or doulbe check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+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 1681528] [NEW] Include information about python versions
Public bug reported: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or doulbe check the versions of /usr/bin/python and /usr/bin/python3. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1681528 Title: Include information about python versions Status in apport package in Ubuntu: New Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or doulbe check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
Hi Paul, https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference. It takes at least 7 days in -proposed before the SRU team will release it. Thanks, Nish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface Status in dnsmasq package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Xenial: Fix Committed Status in network-manager source package in Xenial: Invalid Status in dnsmasq source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Invalid Status in dnsmasq package in Debian: Fix Released Bug description: [Impact] * suspend/resume (which involves disconnection of network devices) leads to dnsmasq failures. [Test Case] * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures upon resume. [Regression Potential] * The fix was NMU'd in Debian in the version immediately after 16.10's. I believe the regression potential is very low as this is a clear bug-fix from upstream. --- Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
Given the current state of Zesty and the proximity to a release day I believe we need patience here heh. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface Status in dnsmasq package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Xenial: Fix Committed Status in network-manager source package in Xenial: Invalid Status in dnsmasq source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Invalid Status in dnsmasq package in Debian: Fix Released Bug description: [Impact] * suspend/resume (which involves disconnection of network devices) leads to dnsmasq failures. [Test Case] * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures upon resume. [Regression Potential] * The fix was NMU'd in Debian in the version immediately after 16.10's. I believe the regression potential is very low as this is a clear bug-fix from upstream. --- Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1679765] Re: cannot lock password for user created with useradd --extrausers
** Changed in: shadow (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1679765 Title: cannot lock password for user created with useradd --extrausers Status in shadow package in Ubuntu: Confirmed Bug description: passwd -l does not take --extrausers or otherwise work for extrausers. Neither does usermod. % mkdir -p /var/lib/extrausers % for f in passwd group gshadow subuid subgid shadow; do touch /var/lib/extrausers/$f; done % useradd foo --extrausers --shell /bin/bash -m % echo $? 0 % # cat /var/lib/extrausers/passwd foo:x:1001:1001::/home/foo:/bin/bash % passwd -l foo passwd: user 'foo' does not exist % passwd --extrausers -l foo passwd: unrecognized option '--extrausers' % usermod --lock foo usermod: user 'foo' does not exist % usermod --extrausers --lock foo usermod: unrecognized option '--extrausers' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 16:34:20 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) Related bugs: * bug 1679777: Adding and reporting ssh keys fails for user in extrausers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1679765/+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 1680811] Re: Request to add wireguard interface to interface-order
** Changed in: resolvconf (Ubuntu) Importance: Undecided => Low ** Changed in: resolvconf (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1680811 Title: Request to add wireguard interface to interface-order Status in resolvconf package in Ubuntu: Triaged Bug description: This started from https://github.com/jlund/streisand/issues/557. Basically wg* namespace is not in interface-order and acts last in * scope, and this makes resolv.conf to stay in the same state. I suggest the following change: :/etc/resolvconf/interface-order # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo +wg* tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* @(br|eth)*([^.]).inet6 @(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)*([^.]).inet @(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
i have an older powerful dell xps with lots of free space.. i believe my partitions are holding me up... i need to allocate more room for the program I believe... trying to figure out how... not totally a Ubuntu knower... but I can learn. :) -- 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 when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. 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 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions 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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
Just curious if there's more work needed here before this fix moves out of proposed and into standard updates for xenial / yakkety, or if not then is there a timeline when that transition is normally expected? I'm currently recommending to users that they reset NetworkManager by hand when they have a DNS error: once this package makes it into the normal update queue then I can just tell them to update their systems. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface Status in dnsmasq package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Xenial: Fix Committed Status in network-manager source package in Xenial: Invalid Status in dnsmasq source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Invalid Status in dnsmasq package in Debian: Fix Released Bug description: [Impact] * suspend/resume (which involves disconnection of network devices) leads to dnsmasq failures. [Test Case] * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures upon resume. [Regression Potential] * The fix was NMU'd in Debian in the version immediately after 16.10's. I believe the regression potential is very low as this is a clear bug-fix from upstream. --- Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
Done: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1681493 Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in Linux Mint: Confirmed Status in upstart : Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Won't Fix Status in mate-settings-daemon package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 LTS, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should upgrade them to Ubuntu 16.04 (see C below). My script is incompatible with these Ubuntu versions - remove it with sudo apt-get purge sysvinit-backlight sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It saves and restores screen and keyboard backlight levels. My script is incompatible with these Ubuntu versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+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 443004] Fw: a piece of useful info
Hi, I found some interesting information that seems to be very useful, check it out here http://tekky.net/alive.php?7978 Speak to you later, gibking -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/443004 Title: Buttons disappear or do not respond to mouse clicks in Eclipse Status in Azureus: Invalid Status in Eclipse: Fix Released Status in LibGTK: Fix Released Status in eclipse package in Ubuntu: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Bug description: After update from alpha 6 to beta Karmic Koala - Eclispe is no longer working correct. It seems to be a problem with GTK. Few buttons are not working - nothing happens when pressing the button or the expected dialog is not shown as expected. I also tested other eclispe package with same result. eclipse 3.5.1 downloaded directly from www.eclipse.org has this bug. Solution: Install eclipse 3.5.1-0ubuntu7 (or later) from the Ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/azureus/+bug/443004/+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 1681517] [NEW] /usr/lib/bluetooth/bluetoothd:11:avdtp_open:endpoint_open_cb:endpoint_reply:complete_pending_call_and_unlock:dbus_connection_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/8a866d2144eff926b451cc11c9018d9c402eceda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety -- 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/1681517 Title: /usr/lib/bluetooth/bluetoothd:11:avdtp_open:endpoint_open_cb:endpoint_reply:complete_pending_call_and_unlock:dbus_connection_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/8a866d2144eff926b451cc11c9018d9c402eceda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681517/+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 1681515] Re: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1681515 Title: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: the update don't want to be complited ProblemType: Package DistroRelease: Ubuntu 15.04 Package: dh-apparmor 2.9.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22 Uname: Linux 3.19.0-84-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 Date: Fri Apr 7 01:33:58 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-04-07 01:32:59 Commandline: aptdaemon role='role-commit-packages' sender=':1.93' Install: linux-headers-3.19.0-84-generic:amd64 (3.19.0-84.92), linux-headers-3.19.0-84:amd64 (3.19.0-84.92), linux-image-extra-3.19.0-84-generic:amd64 (3.19.0-84.92), linux-image-3.19.0-84-generic:amd64 (3.19.0-84.92) Upgrade: linux-headers-generic:amd64 (3.19.0.82.80, 3.19.0.84.82), google-chrome-stable:amd64 (57.0.2987.98-1, 57.0.2987.133-1), linux-libc-dev:amd64 (3.19.0-82.90, 3.19.0-84.92), linux-image-generic:amd64 (3.19.0.82.80, 3.19.0.84.82) DuplicateSignature: package:dh-apparmor:2.9.1-0ubuntu9:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-30 (527 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-84-generic root=UUID=9ce7fb5a-2b9f-407f-bcd0-b256764f29c4 ro quiet splash RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: apparmor Syslog: Apr 10 19:07:10 zambla dbus[688]: [system] AppArmor D-Bus mediation is enabled Title: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1681515/+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 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered
It is one device. We have 2 luns for 2 different ocfs2 filesystems mounted on all servers (6) in the cluster. It is presented via fiber channel from our SAN. I think the issue is that if you run fstrim from all servers which are mounting the same ocfs2 filesystem at the same time, bad stuff happens. We are using multipth: WWPN-THINGEE-HERE dm-3 TEGILE,INTELLIFLASH size=2.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=active | |- 0:0:0:16 sdb 8:16 active ready running | `- 1:0:0:16 sdf 8:80 active ready running `-+- policy='round-robin 0' prio=1 status=enabled |- 0:0:1:16 sdd 8:48 active ready running `- 1:0:1:16 sdh 8:112 active ready running WWPN-THINGEE-HERE dm-2 TEGILE,INTELLIFLASH size=2.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=active | |- 0:0:1:15 sdc 8:32 active ready running | `- 1:0:1:15 sdg 8:96 active ready running `-+- policy='round-robin 0' prio=1 status=enabled |- 0:0:0:15 sda 8:0 active ready running `- 1:0:0:15 sde 8:64 active ready running -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1681410 Title: fstrim corrupts ocfs2 filesystems when clustered Status in util-linux package in Ubuntu: Incomplete Bug description: Recently upgraded from trusty to xenial and found that our ocfs2 filesystems, which are mounted across a number of nodes simultaneously, would become corrupt on the weekend: [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-2): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:35 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:35 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = -30 [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-3): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:36 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:36 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status = -30 We found the cron.weekly job which is pretty close to the timing: 47 6* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) # cat /etc/cron.weekly/fstrim #!/bin/sh # trim all mounted file systems which support it /sbin/fstrim --all || true We have disabled this job across our servers running clustered ocfs2 filesystems. I think either the utility or the cronjob should ignore ocfs2 (gfs too?) filesystems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1681410/+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 1681515] [NEW] package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: the update don't want to be complited ProblemType: Package DistroRelease: Ubuntu 15.04 Package: dh-apparmor 2.9.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22 Uname: Linux 3.19.0-84-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 Date: Fri Apr 7 01:33:58 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-04-07 01:32:59 Commandline: aptdaemon role='role-commit-packages' sender=':1.93' Install: linux-headers-3.19.0-84-generic:amd64 (3.19.0-84.92), linux-headers-3.19.0-84:amd64 (3.19.0-84.92), linux-image-extra-3.19.0-84-generic:amd64 (3.19.0-84.92), linux-image-3.19.0-84-generic:amd64 (3.19.0-84.92) Upgrade: linux-headers-generic:amd64 (3.19.0.82.80, 3.19.0.84.82), google-chrome-stable:amd64 (57.0.2987.98-1, 57.0.2987.133-1), linux-libc-dev:amd64 (3.19.0-82.90, 3.19.0-84.92), linux-image-generic:amd64 (3.19.0.82.80, 3.19.0.84.82) DuplicateSignature: package:dh-apparmor:2.9.1-0ubuntu9:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-30 (527 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-84-generic root=UUID=9ce7fb5a-2b9f-407f-bcd0-b256764f29c4 ro quiet splash RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: apparmor Syslog: Apr 10 19:07:10 zambla dbus[688]: [system] AppArmor D-Bus mediation is enabled Title: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1681515 Title: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: the update don't want to be complited ProblemType: Package DistroRelease: Ubuntu 15.04 Package: dh-apparmor 2.9.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22 Uname: Linux 3.19.0-84-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 Date: Fri Apr 7 01:33:58 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-04-07 01:32:59 Commandline: aptdaemon role='role-commit-packages' sender=':1.93' Install: linux-headers-3.19.0-84-generic:amd64 (3.19.0-84.92), linux-headers-3.19.0-84:amd64 (3.19.0-84.92), linux-image-extra-3.19.0-84-generic:amd64 (3.19.0-84.92), linux-image-3.19.0-84-generic:amd64 (3.19.0-84.92) Upgrade: linux-headers-generic:amd64 (3.19.0.82.80, 3.19.0.84.82), google-chrome-stable:amd64 (57.0.2987.98-1, 57.0.2987.133-1), linux-libc-dev:amd64 (3.19.0-82.90, 3.19.0-84.92), linux-image-generic:amd64 (3.19.0.82.80, 3.19.0.84.82) DuplicateSignature: package:dh-apparmor:2.9.1-0ubuntu9:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-30 (527 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-84-generic root=UUID=9ce7fb5a-2b9f-407f-bcd0-b256764f29c4 ro quiet splash RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: apparmor Syslog: Apr 10 19:07:10 zambla dbus[688]: [system] AppArmor D-Bus mediation is enabled Title: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1681515/+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 1599601] Re: courier-authdaemon not enabled by default to start
** Changed in: xorg (Ubuntu) Importance: Undecided => High -- 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/1599601 Title: courier-authdaemon not enabled by default to start Status in xorg package in Ubuntu: Confirmed Bug description: The service authdaemond is not started by default at startup. I had to use the following command so the service was started at startup : $> sudo systemctl enable courier-authdaemon.service Then the courier-imap with no particular authentification (ie through authdaemon) method was able to work perfectly! To give more details, the error encountered was that I wasn't able to use the imap over ssl (although it worked perfectly up to 15.10 with nothing special to do) In /var/log/syslog, the logged lines that appeared each time my mail client was trying to access to the local imap server were: imapd-ssl: authdaemon: s_connect() failed: No such file or directory imapd-ssl: LOGIN FAILED, user=JR, ip=[:::192.168.1.254] imapd-ssl: authentication error: No such file or directory The release is: Description:Ubuntu 16.04 LTS Release:16.04 courier-authdaemon: Installé : 0.66.4-3build1 Candidat : 0.66.4-3build1 Table de version : *** 0.66.4-3build1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status I expected that the service was started automatically at startup. What happened instead was it was not enabled, leading to this mess on my kubuntu installation. So if the package's maintainer could check whether on a usual install( maybe this happened only on my computer) this service was enabled by default, that could help other people. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 4 20:19:02 2016 InstallationDate: Installed on 2016-05-25 (40 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1599601/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager
@Alberto, why did you mark the samba task critical? As far as I can tell, there is no bug in samba itself, all of these bugs are in update-manager and just have been seen with various binary packages which we're marking this bug and then indicating they are invalid. ** Changed in: samba (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: "Use of uninitialized value" in debconf via update-manager Status in debconf package in Ubuntu: Invalid Status in php7.0 package in Ubuntu: Invalid Status in samba package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1681158] Re: package python-six 1.10.0-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
>From log: Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' appears numerous times -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1681158 Title: package python-six 1.10.0-3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in six package in Ubuntu: Incomplete Bug description: It crashed when I had open my laptop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 21 16:45:06 2017 Dependencies: ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-03-15 (24 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1681158/+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 1681158] Re: package python-six 1.10.0-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Thank you for taking the time to file a bug report. I was unable to reproduce this using apt and on a lxd image of xenial. Using apt to update and install the package may get you past this. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". ** Changed in: six (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1681158 Title: package python-six 1.10.0-3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in six package in Ubuntu: Incomplete Bug description: It crashed when I had open my laptop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 21 16:45:06 2017 Dependencies: ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-03-15 (24 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1681158/+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 1681504] [NEW] package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Public bug reported: nothing happened I guess. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 9 19:53:33 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationDate: Installed on 2016-07-27 (256 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: console-setup Title: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.keyboard-setup: [deleted] ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1681504 Title: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in console-setup package in Ubuntu: New Bug description: nothing happened I guess. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 9 19:53:33 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationDate: Installed on 2016-07-27 (256 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: console-setup Title: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.keyboard-setup: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1681504/+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 1547109] Re: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] Underruns, dropouts or crackling sound
** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Medium -- 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/1547109 Title: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Confirmed Bug description: To reproduce play Audio CD using Rhythmbox. I noticed that the audio is crackling (not overdriven, nor skipping.) However I can play the audio tracks fine with Totem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: arges 1968 F...m pulseaudio /dev/snd/controlC0: arges 1968 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 18 11:01:16 2016 InstallationDate: Installed on 2015-09-04 (167 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150903) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: SKLSE2R1.R00.B089.B00.1506160228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Skylake DT DDR4 RVP8 dmi.board.vendor: Intel Corp. dmi.board.version: 1 dmi.chassis.asset.tag: Un-Supported dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrSKLSE2R1.R00.B089.B00.1506160228:bd06/16/2015:svnIntelCorporation:pnSkylakeClientplatform:pvr0.1:rvnIntelCorp.:rnSkylakeDTDDR4RVP8:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Skylake Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547109/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager
** Changed in: samba (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: "Use of uninitialized value" in debconf via update-manager Status in debconf package in Ubuntu: Invalid Status in php7.0 package in Ubuntu: Invalid Status in samba package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1681493] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859735/+files/Lspci.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859739/+files/ProcInterrupts.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859746/+files/SystemdDelta.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859745/+files/ProcModules.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859737/+files/ProcCpuinfoMinimal.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859738/+files/ProcEnviron.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859747/+files/UdevDb.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859734/+files/JournalErrors.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859733/+files/Dependencies.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859736/+files/ProcCpuinfo.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. --- ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-02 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G752VS NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: systemd 232-21ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VS.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VS 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G752VS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1681493] Re: Ubuntu Zesty: Problem With Screen Brightness Settings
apport information ** Tags added: apport-collected zesty ** Description changed: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. + --- + ApportVersion: 2.20.4-0ubuntu3 + Architecture: amd64 + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-01-02 (98 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. + Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. + Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. G752VS + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: systemd 232-21ubuntu2 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 + Tags: zesty + Uname: Linux 4.10.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 10/19/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: G752VS.306 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: G752VS + 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.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.name: G752VS + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1681493/+attachment/4859732/+files/CurrentDmesg.txt -- 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backl
[Touch-packages] [Bug 1681493] Re: Ubuntu Zesty: Problem With Screen Brightness Settings
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided Status: 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/1681493 Title: Ubuntu Zesty: Problem With Screen Brightness Settings Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Non-Optimus laptop ASUS G752VS (Nvidia GTX1070) Ubuntu 17.04 Xorg-Server-1.19.3 Nvidia driver 375.39 Situation on 2017-04-05: Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen brightness, but after restarting the screen brightness of my laptop resets to maximum. Situation on 2017-04-08: Today I received many Ubuntu updates (kernel included), and I also installed freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - Proprietary GPU Drivers PPA). Now brightness settings are correctly saved, but I have a new problem: changing brightness level doesn't produce any effect (both with or without Nvidia driver installed) Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and "acpi_video1" ~$ systemctl status systemd-backlight@backlight:acpi_video0.service ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago Docs: man:systemd-backlight@.service(8) Main PID: 683 (code=exited, status=0/SUCCESS) ~$ systemctl status systemd-backlight@backlight:acpi_video1.service ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen Backlight B Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendo Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago Docs: man:systemd-backlight@.service(8) Main PID: 684 (code=exited, status=0/SUCCESS) Situation on 2017-04-10: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initial problem: I can again adjust the screen brightness, but after restarting the screen brightness of my laptop again resets to maximum. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+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 1516531] Re: Fullscreen Freeze.
In CompizConfig Settings Manager and tab Composite plugin helps to DISABLE "Unredirect Fullscreen Windows". KODI doesn't crash with this settings in fullscreen mode. -- 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/1516531 Title: Fullscreen Freeze. Status in xorg package in Ubuntu: Confirmed Bug description: Related?: http://askubuntu.com/questions/692405/ubuntu-15-10-unity-freezes-after-escaping-full-screen-video https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622 I've been having cases of unusual screen behavior, particularly when Kodi 16 is being used (maybe it's just a Kodi thing). There have been times before when coming out of fullscreen video using either Chrome or Kodi would drop me to a console screen with no input. I think I would be able to kill the gnome session in tty1. Now, after a bios upgrade as well as the latest display manager and kernel update, Kodi has frozen in fullscreen a couple of times and yet audio will still play from Kodi. I created the bug report in tty1. I've also been noticing that if I pause a Kodi video, other non-Kodi applications may not update their window content. For example, I may be in a webpage in Chrome and I try to mousewheel scroll, yet not see the scrolling effect. Or I will click on a different tab and the window doesn't show the switch. BUT, if I continue playing the Kodi video, Chrome will update it's screen, and if I switch back to the tab I scrolled, the scroll will have already occurred. I will say that I have at least not had a fullscreen GUI crash me out to console. Another peculiarity is when booting Ubuntu, I used to be able to press ESC to view the kernel/system booting output, but now it just shows a black screen with a cursor. The downside to that in 15.04 was I'd lose my mouse cursor when the GUI login screen came up. Let me know what other output you'd like (or whatever test you'd like me to try) "when" it happens again. --- .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:041e] InstallationDate: Installed on 2015-10-28 (26 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash elevator=cfq vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H97M-ITX/ac 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.80:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac: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. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1
[Touch-packages] [Bug 1473178] Re: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Changed in: python-setuptools (Ubuntu) Assignee: (unassigned) => Barry Warsaw (barry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1473178 Title: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in python-setuptools package in Ubuntu: Confirmed Bug description: crash on login ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-pkg-resources 3.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Wed Jul 8 23:04:00 2015 Dependencies: DuplicateSignature: package:python-pkg-resources:3.3-1ubuntu1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-06 (32 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: python-setuptools Title: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1473178/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: "Use of uninitialized value" in debconf via update-manager Status in debconf package in Ubuntu: Invalid Status in php7.0 package in Ubuntu: Invalid Status in samba package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
I also have Skylake laptop (ASUS GL502VM) with a GTX 1060 which is always in Discrete mode (I can't use it in hybrid mode at all) and I have the same or similar problem (HDMI video: Ok / HDMI audio: Doesn't work). In my case "lspci -H1" doesn't even list the NVIDIA Audio device. Any idea of how to fix this? ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ 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/1377653/+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 1473178] Re: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
This looks like another case where pyclean (not py3clean) might be getting called by Python 3, which clearly won't work. Investigating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1473178 Title: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in python-setuptools package in Ubuntu: Confirmed Bug description: crash on login ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-pkg-resources 3.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Wed Jul 8 23:04:00 2015 Dependencies: DuplicateSignature: package:python-pkg-resources:3.3-1ubuntu1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-06 (32 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: python-setuptools Title: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1473178/+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 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
Nvidia 375.39 -> systemd Nvidia 381.09 -> nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in Linux Mint: Confirmed Status in upstart : Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Won't Fix Status in mate-settings-daemon package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 LTS, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should upgrade them to Ubuntu 16.04 (see C below). My script is incompatible with these Ubuntu versions - remove it with sudo apt-get purge sysvinit-backlight sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It saves and restores screen and keyboard backlight levels. My script is incompatible with these Ubuntu versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+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 1680974] Re: libegl1-mesa depends on libmirclient9
I don't know exactly how that calculation is done. But it would be nice to be able to uninstall the Mir packages without it removing Mesa. -- 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/1680974 Title: libegl1-mesa depends on libmirclient9 Status in mesa package in Ubuntu: Invalid Bug description: Mir is dead. libegl1-mesa should no longer depend on it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libegl1-mesa 17.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Fri Apr 7 23:55:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1197 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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: Fri Apr 7 20:23:48 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1680974/+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 1680974] Re: libegl1-mesa depends on libmirclient9
the dependencies are calculated automatically by dh_shlibdeps, so no -- 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/1680974 Title: libegl1-mesa depends on libmirclient9 Status in mesa package in Ubuntu: Invalid Bug description: Mir is dead. libegl1-mesa should no longer depend on it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libegl1-mesa 17.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Fri Apr 7 23:55:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1197 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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: Fri Apr 7 20:23:48 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1680974/+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 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered
I'm thinking that the bug is in the OCFS2 filesystem driver. Since it can span multiple disks, both local and remote, it can not give a sensible answer to the FIBMAP ioctl when fstrim asks what blocks a file is located in. Please test this by creating a file and checking where FIBMAP says it is located and see if the data is really there: echo hello > foo hdparm --fibmap foo dd count=1 bs=size if=/dev/dm-2 skip=offset | hd Where size is whatever the block size of the filesystem is ( 4k? ), and offset is the block number given by the hdparm call. Am I correct in assuming this filesystem spans at least two devices? dm-2 and dm-3? ** Changed in: util-linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1681410 Title: fstrim corrupts ocfs2 filesystems when clustered Status in util-linux package in Ubuntu: Incomplete Bug description: Recently upgraded from trusty to xenial and found that our ocfs2 filesystems, which are mounted across a number of nodes simultaneously, would become corrupt on the weekend: [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-2): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:35 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:35 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = -30 [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-3): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:36 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:36 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status = -30 We found the cron.weekly job which is pretty close to the timing: 47 6* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) # cat /etc/cron.weekly/fstrim #!/bin/sh # trim all mounted file systems which support it /sbin/fstrim --all || true We have disabled this job across our servers running clustered ocfs2 filesystems. I think either the utility or the cronjob should ignore ocfs2 (gfs too?) filesystems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1681410/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting
Upstream kernel test - kernel 4.11-rc6 boot-time >3 min. no local login only remote-login brigthness adjustment: not possible HDMI not usable (not new) 40 error and fail lines - compared to 2017-04-04 (rc5) - minimal differences ** Tags removed: kernel-bug-exists-upstream-4.11-rc5 ** Tags added: kernel-bug-exists-upstream-4.11-rc6 -- 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/1639517 Title: [HP Pavilion Notebook - 17-g164ng] black screen when booting Status in xorg package in Ubuntu: Confirmed Bug description: When booting the screen is black – backlight on – off - on. When HDD is inactive - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del - remote access e.g. using ssh is possible Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10. My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz. It seems very similar to that described in #1597079. The bug report was generated from a remote PC. My HP notebook was started without any workaround parameters. This apport doesn't display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa. WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver. WORKAROUND: When booting in UEFI mode, use kernel parameters: nomodeset or: nomodeset xforcevesa Resolution without xforcevesa: 800x600 Resolution with xforcevesa: 1600x900 – the optimal resolution ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 5 23:40:19 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b6] InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.41 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B6 dmi.board.vendor: HP dmi.board.version: 81.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Nov 5 23:32:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
** Changed in: ufrs-apt Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: hud (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in unbuntu-fr Scripts - apt: Confirmed Status in hud package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.
[Touch-packages] [Bug 1280372] Re: Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU
** Changed in: hud Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: libdbusmenu-qt Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: hud (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: libdbusmenu-qt (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1280372 Title: Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU Status in Unity HUD: In Progress Status in libdbusmenu-qt: Fix Released Status in hud package in Ubuntu: Fix Released Status in libdbusmenu-qt package in Ubuntu: Fix Released Bug description: See the following debug output: * http://paste.ubuntu.com/6931329/ * http://paste.ubuntu.com/6931331/ * http://paste.ubuntu.com/6931338/ * http://paste.ubuntu.com/7151579/ 14:09:09 QVariantMap DBusMenuExporterDBus::getProperties(int, const QStringList&) const: Condition failed: action 14:09:09 bool DBusMenuExporterDBus::AboutToShow(int): Condition failed: menu Was also seen in the console. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1280372/+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 1327419] Re: Infographic's language not updated until the metric value is changed
** Changed in: canonical-devices-system-image Assignee: Thomas Strehl (strehl-t) => (unassigned) ** Changed in: camera-app (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: music-app Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: libusermetrics (Ubuntu RTM) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: libusermetrics (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1327419 Title: Infographic's language not updated until the metric value is changed Status in Canonical System Image: Fix Released Status in Ubuntu Music App: In Progress Status in Ubuntu Translations: Triaged Status in camera-app package in Ubuntu: In Progress Status in libusermetrics package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu RTM: Fix Released Bug description: 1) Start the music app 2) Play a track for more than 10 seconds to trigger the metric update 3) Lock and unlock to show the infographic 4) Note, for example, "1 song played today" appears (double tap to cycle through to find music if required) 5) Goto system settings and change the language 6) Restart the device 7) Note the infographic's language has not been updated and it still states '1 song played today' 8) Start the music app 9) Play a track for more than 10 seconds to trigger the metric update 10) Lock and unlock to show the infographic 11) Now notice the infographic's language is now correct, for example "2 Morceaux joues aujourd'hui" It was expected that step 7 the infographic would show the correct language. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1327419/+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 1597681] Re: [CTA] Enable WAPI support
** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- 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/1597681 Title: [CTA] Enable WAPI support Status in Canonical System Image: In Progress Status in indicator-network package in Ubuntu: In Progress Status in network-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: The phone does not currently support WAPI [1] It should do so. As part of this, support for the SMS4 [2] cipher is also required. [1] https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure [2]: https://en.wikipedia.org/wiki/SMS4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+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 1670408] Re: Missing apparmor rules cause tor to fail to start
I can no longer reproduce the original problem on current Zesty. I also tried downgrading to what I think would have been active at the time of my original report (tor and kernel versions known; I hadn't noted the apparmor version though). This is as below, but I still cannot reproduce. root@test:~# dpkg-query -W tor tor 0.2.9.9-1ubuntu1 root@test:~# dpkg-query -W apparmor apparmor2.11.0-2ubuntu1 root@test:~# uname -a Linux test 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux It definitely was reproducible in my original report. I have not been able to pin down what changed, so marking Incomplete for now, as it could be me or my environment. But for now, tor appears to be working correctly by default on Zesty, which was my goal in tackling this. ** Changed in: tor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1670408 Title: Missing apparmor rules cause tor to fail to start Status in apparmor package in Ubuntu: New Status in tor package in Ubuntu: Incomplete Bug description: Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor fails to start after installing the tor package. "systemctl status tor@default" reports: Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, code=killed, status=11/SEGV Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network for TCP. Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed state. Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 'signal'. There are two AppArmor denials in the kernel log: Mar 6 15:53:12 zesty-test kernel: [ 102.699647] audit: type=1400 audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-zesty_" profile="system_tor" name="/run/systemd/journal/stdout" pid=3520 comm="tor" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10 Mar 6 15:53:12 zesty-test kernel: [ 102.702418] audit: type=1400 audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap" namespace="root//lxd-zesty_" profile="system_tor" name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m" denied_mask="m" fsuid=10 ouid=10 Workaround: add the following two lines to /etc/apparmor.d/system_tor: /usr/bin/tor m, /run/systemd/journal/stdout rw, I couldn't remember how to that that profile reloaded, so I rebooted, and after the reboot tor does start up successfully. "systemctl tor@default" reports it as running. I haven't checked to see if only one or other rule is actually required. Importance -> High since this bug makes the package unusable in its default configuration on Zesty. Since the AppArmor profile comes from Debian's 0.2.9.9-1, this should probably be fixed in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1636395] Re: dnsmasq not working with OpenVPN
I mean not give up with dnscrypt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1636395 Title: dnsmasq not working with OpenVPN Status in dnsmasq package in Ubuntu: Confirmed Status in openvpn-systemd-resolved package in Ubuntu: Confirmed Bug description: I'm using OpenVPN configured with Network Manager. My VPN have a DNS server configured by OpenVPN and config pushed by it while connecting. This server is not registered by dnsmasq so domain names are not resolved but pinging by IP address works. When I test name resolving by pointing to DNS server (172.16.1.1) from VPN provider it's works. For example: $ host google.com 172.16.1.1 Using domain server: Name: 172.16.1.1 Address: 172.16.1.1#53 Aliases: google.com has address 172.217.0.174 google.com has IPv6 address 2607:f8b0:400b:807::200e google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. But if I test without pointing DNS server is not working: $ host google.com ;; connection timed out; no servers could be reached My /etc/resolv.conf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 To repair this bug I have to kill dnsmasq and it's automatically reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1636395/+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 1680784] Re: Glitches
** Description changed: - I switch pc to sleep? then i wake up him, now i get glitchs lines, if i + I switch pc to sleep, then i wake up him, now i get glitchs lines, if i reboot pc, lines will lost. There is screenshot of screen with glitch https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing ProblemType: Graphic glitch DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Date: Fri Apr 7 13:12:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 610] [1462:809f] InstallationDate: Installed on 2017-03-22 (15 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=ru PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5ab9fb9f-7d9b-4ec4-ab26-936456251d31 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0113 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM DH dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0113:bd03/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Fri Apr 7 10:17:12 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB OPTICAL MOUSEMOUSE, id 8 inputLogitech K270KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 -- 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/1680784 Title: Glitches Status in xorg package in Ubuntu: New Bug description: I switch pc to sleep, then i wake up him, now i get glitchs lines, if i reboot pc, lines will lost. There is screenshot of screen with glitch https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing ProblemType: Graphic glitch DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-ge
[Touch-packages] [Bug 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1681410 Title: fstrim corrupts ocfs2 filesystems when clustered Status in util-linux package in Ubuntu: Confirmed Bug description: Recently upgraded from trusty to xenial and found that our ocfs2 filesystems, which are mounted across a number of nodes simultaneously, would become corrupt on the weekend: [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-2): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:35 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:35 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = -30 [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-3): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:36 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:36 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status = -30 We found the cron.weekly job which is pretty close to the timing: 47 6* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) # cat /etc/cron.weekly/fstrim #!/bin/sh # trim all mounted file systems which support it /sbin/fstrim --all || true We have disabled this job across our servers running clustered ocfs2 filesystems. I think either the utility or the cronjob should ignore ocfs2 (gfs too?) filesystems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1681410/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
I also have this problem and it is stupid to have watchdog started manually using systemd after each (re)boot to work. I have removed all blacklist-entries for iTCO_wdt and also rebuild initramfs ... but it still says at boot that module is blacklisted ... :-( -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Confirmed Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 1599601] Re: courier-authdaemon not enabled by default to start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1599601 Title: courier-authdaemon not enabled by default to start Status in xorg package in Ubuntu: Confirmed Bug description: The service authdaemond is not started by default at startup. I had to use the following command so the service was started at startup : $> sudo systemctl enable courier-authdaemon.service Then the courier-imap with no particular authentification (ie through authdaemon) method was able to work perfectly! To give more details, the error encountered was that I wasn't able to use the imap over ssl (although it worked perfectly up to 15.10 with nothing special to do) In /var/log/syslog, the logged lines that appeared each time my mail client was trying to access to the local imap server were: imapd-ssl: authdaemon: s_connect() failed: No such file or directory imapd-ssl: LOGIN FAILED, user=JR, ip=[:::192.168.1.254] imapd-ssl: authentication error: No such file or directory The release is: Description:Ubuntu 16.04 LTS Release:16.04 courier-authdaemon: Installé : 0.66.4-3build1 Candidat : 0.66.4-3build1 Table de version : *** 0.66.4-3build1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status I expected that the service was started automatically at startup. What happened instead was it was not enabled, leading to this mess on my kubuntu installation. So if the package's maintainer could check whether on a usual install( maybe this happened only on my computer) this service was enabled by default, that could help other people. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 4 20:19:02 2016 InstallationDate: Installed on 2016-05-25 (40 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1599601/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Alright, yes lets hope. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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 1621216] Re: [MIR] geoclue-2.0
** Changed in: iio-sensor-proxy (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is a bug assignee. https://bugs.launchpad.net/bugs/1621216 Title: [MIR] geoclue-2.0 Status in geoclue package in Ubuntu: New Status in geoclue-2.0 package in Ubuntu: Fix Released Status in iio-sensor-proxy package in Ubuntu: Fix Released Bug description: libqt5positioning5 now recommends geoclue-2.0 +qtlocation-opensource-src (5.6.0-1) experimental; urgency=medium + + [ Lisandro Damián Nicanor Pérez Meyer ] + * New upstream release. +- Bump Qt build dependencies. + * Make qtlocation5-examples depend on qml-module-qtpositioning. + * Make libqt5positioning5 recommend geoclue-2.0. It will connect to it by +using dbus. geoclue-2.0 was previously in main see the MIR for it in bug #1388294. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/1621216/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
I think this askUbuntu thread may help you. http://askubuntu.com/questions/345588/what-is-the-safest-way-to-clean-up-boot-partition -- 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 when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. 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 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions 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 1680974] Re: libegl1-mesa depends on libmirclient9
But Mir is not really used and never really was. It was available as a preview. It would make sense to relax the dependency from required to suggested, if not drop it entirely as a dependency but still have it in the repository. Yes, I read that it is not going away in the short term and it is getting continued maintenance for IOT. -- 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/1680974 Title: libegl1-mesa depends on libmirclient9 Status in mesa package in Ubuntu: Invalid Bug description: Mir is dead. libegl1-mesa should no longer depend on it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libegl1-mesa 17.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Fri Apr 7 23:55:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1197 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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: Fri Apr 7 20:23:48 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1680974/+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 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly
** Changed in: ubuntu-z-systems Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1679691 Title: libseccomp fix - s390: handle multiplexed syscalls correctly Status in Ubuntu on IBM z Systems: Confirmed Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Xenial: New Status in libseccomp source package in Yakkety: New Status in libseccomp source package in Zesty: Confirmed Status in libseccomp source package in aa-series: New Bug description: Within Xenial version 2.2.3 of seccomp is included. With Yaketty version 2.3.1 is available and fixed this problem. Even Docker is working on a SNAP solution, please provide the fix to 16.04. With following patches this can be applied to 2.2.3 in support of the 16.04 LTS Release 16.04 Here the upstream git commits for the patches: 0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch 1d63fad4a064b80e0b921b16ed419f3342337ed4 0001-all-block-negative-syscall-numbers-from-the-filter.patch 51c46f80c1edee863bbc4eb21b03decc44e69a45 0001-api-limit-errno-values-to-MAX_ERRNO.patch 0d287caf43792239b107ee3215b32b8bc901f9c3 0001-db-fix-a-minor-style-problem.patch 61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 0001-db-make-the-individual-db-filter-ops-private.patch a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16 0001-db-store-the-rules-used-to-build-the-filter.patch f16f405f61ecdbad202257b61004b85fce64d75c 0001-arch-make-use-of-function-tables-instead-of-switch-s.patch 57df79c166b26d5044e7e27099e6e69671e727dd 0001-db-introduce-transaction-support.patch 9be1538a4ac0e45047a3f1b79691505c3d11ca31 0001-arch-move-the-low-level-filter-rule-addition-code-in.patch 996e445a74823c735757413fda809e1ed0afc7d4 0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch 5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 0001-arch-basic-support-for-multiplexed-and-direct-socket.patch d32c3bfa4b07add90dcd04292eb4ba278dd103ba 0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch 983835f3e0fd000a42c8beaea9d7fbe72665 0001-tests-add-a-test-for-the-different-types-of-socket-s.patch 099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 0001-api-add-a-seccomp_version-API-call.patch 58a7c20d4c2defc1c984c5c7391ecc60093f85fa 0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch 8ed78c3859f476d302995b43d6739f3341f5b37d 0001-s390-handle-multiplexed-syscalls-correctly.patch 47516603828396f85107ea3e2a254958c2bc3ff5 0001-arch-fix-the-multiplexed-ipc-syscalls.patch 3a89bd144885f54aff86f2e275859a1483992edd With the following additional commit all tests pass with "make check" 0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch 0d8504bc192e0989494df06efc4b186a9f02e20a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679691/+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 1681410] [NEW] fstrim corrupts ocfs2 filesystems when clustered
Public bug reported: Recently upgraded from trusty to xenial and found that our ocfs2 filesystems, which are mounted across a number of nodes simultaneously, would become corrupt on the weekend: [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-2): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:35 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:35 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = -30 [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-3): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:36 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:36 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status = -30 We found the cron.weekly job which is pretty close to the timing: 47 6* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) # cat /etc/cron.weekly/fstrim #!/bin/sh # trim all mounted file systems which support it /sbin/fstrim --all || true We have disabled this job across our servers running clustered ocfs2 filesystems. I think either the utility or the cronjob should ignore ocfs2 (gfs too?) filesystems. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: fstrim ocfs2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1681410 Title: fstrim corrupts ocfs2 filesystems when clustered Status in util-linux package in Ubuntu: New Bug description: Recently upgraded from trusty to xenial and found that our ocfs2 filesystems, which are mounted across a number of nodes simultaneously, would become corrupt on the weekend: [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-2): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:35 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:35 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = -30 [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-3): ocfs2_validate_gd_self: Group descriptor #516096 has bad signature [Sun Apr 9 06:46:36 2017] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [Sun Apr 9 06:46:36 2017] OCFS2: File system is now read-only. [Sun Apr 9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status = -30 We found the cron.weekly job which is pretty close to the timing: 47 6* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) # cat /etc/cron.weekly/fstrim #!/bin/sh # trim all mounted file systems which support it /sbin/fstrim --all || true We have disabled this job across our servers running clustered ocfs2 filesystems. I think either the utility or the cronjob should ignore ocfs2 (gfs too?) filesystems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1681410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in Linux Mint: Confirmed Status in upstart : Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Won't Fix Status in mate-settings-daemon package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 LTS, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should upgrade them to Ubuntu 16.04 (see C below). My script is incompatible with these Ubuntu versions - remove it with sudo apt-get purge sysvinit-backlight sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It saves and restores screen and keyboard backlight levels. My script is incompatible with these Ubuntu versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+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 1680974] Re: libegl1-mesa depends on libmirclient9
I know he did. There's no need to have a bug for it, the dep will be dropped when Mir is no longer used. And if you read further you've probably seen that Mir is not going away in the short term at least. -- 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/1680974 Title: libegl1-mesa depends on libmirclient9 Status in mesa package in Ubuntu: Invalid Bug description: Mir is dead. libegl1-mesa should no longer depend on it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libegl1-mesa 17.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Fri Apr 7 23:55:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1197 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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: Fri Apr 7 20:23:48 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1680974/+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 997200] Re: Add NetworkManager connectivity config package
** Changed in: network-manager (Debian) Status: Unknown => New -- 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/997200 Title: Add NetworkManager connectivity config package Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in network-manager source package in Precise: Won't Fix Status in update-manager source package in Precise: Won't Fix Status in network-manager source package in Quantal: Won't Fix Status in update-manager source package in Quantal: Won't Fix Status in network-manager source package in Raring: Won't Fix Status in update-manager source package in Raring: Won't Fix Status in network-manager package in Debian: New Bug description: Feature === A separate network-manager-config-connectivity package that contains the 3-line config snippet to enable NetworkManager's connectivity check. This is the same approach taken by Fedora since 2014 (their package is named config-connectivity-fedora). jbicha would like to have ubuntu-gnome-desktop recommend this package for zesty. With this config, GNOME Shell will popup a browser page when a captive portal is detected. The browser page is powered by webkit2gtk. https://help.gnome.org/misc/release-notes/3.14/#captive-portals By making it a separate package, it is very easy for Ubuntu flavors to opt in to installing it by default if they choose. And it's very easy for users to opt in or out without needing to mess around with system configuration files. This new feature (and how to opt out) will be mentioned in Ubuntu GNOME's Release Notes. Enabling the connectivity check by default for all of Ubuntu was discussed almost 5 years ago: https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html Link to new discussion: https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html Git merge proposal attached. Original Bug Report == When in a hotel there is a often a T&Cs page that is delivered when connecting to the network. Some combination of network manager and update manager (or something else entirely) doesn't seem to be able to handle this, and update are left in a non-working state after not being able to read package headers file. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 17:27:02 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IpRoute: default via 10.155.32.1 dev wlan0 proto static 10.155.32.0/19 dev wlan0 proto kernel scope link src 10.155.38.82 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/997200/+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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi, G.M. > Opening this file with less, the ngoing up & down with arrows or pgup/pgdown, you'll notice that the lines with '>>>' will merge into a single line. I cannot reproduce it on gnome-terminal 70x24. 1. Could you upload your reproducible file? 2. What about terminal software and its window size? 3. If use "less -N file", what it will be? Thanks, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
I hope they will just approve the later upload, and both fixes will make it into -proposed and then -updates together. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
No problem, please just tell me against which package? In the meantime, here's the new confusion: I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via additional drivers. Now the situation has returned to initially reported problem: everything is ok with adjusting screen brightness, but Ubuntu 17.04 again doesn't save my brightness settings after reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions Status in Dell Sputnik: New Status in One Hundred Papercuts: Won't Fix Status in Linux Mint: Confirmed Status in upstart : Confirmed Status in cinnamon-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Won't Fix Status in mate-settings-daemon package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Won't Fix Bug description: HOW TO REPRODUCE: 1. Boot a laptop. 2. Set a different screen (or keyboard) backlight brightness level. 3. Reboot. RESULT: Backlight is not memorized. FIX: A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight sudo apt-get update sudo apt-get install sysvinit-backlight NOTES: 1. If you have installed previous non-deb version, please remove it carefully manually sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness /etc/rc?.d/?25brightness 2. If you have installed previous version from my PPA on Ubuntu 14.04 LTS, please reinstall the package by: sudo apt-get purge sysvinit-backlight sudo apt-get install sysvinit-backlight 3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too. B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should upgrade them to Ubuntu 16.04 (see C below). My script is incompatible with these Ubuntu versions - remove it with sudo apt-get purge sysvinit-backlight sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It saves and restores screen and keyboard backlight levels. My script is incompatible with these Ubuntu versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+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 1637684] Re: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt
** Changed in: dpkg (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637684 Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt Status in base-files package in Ubuntu: Incomplete Status in dpkg package in Ubuntu: Incomplete Bug description: I don'know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 29 02:11:08 2016 Dependencies: Df: Filesystem 1K-blocks Used Available Use% Mounted on udev 8036636 0 8036636 0% /dev ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2016-10-29 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: base-files Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637684/+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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
OK... Just tried to test the new package # apt-get install less Reading package lists... Done Building dependency tree Reading state information... Done less is already the newest version (481-2.1ubuntu2). But the problem is still there, so the patch is unsufficient -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi, I think I have the same bug. What happens is the following: Example file Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview cleanTitle FINER: >>> AFTER QUOTE=realtime hand tracking using modificated flocks of features algorithm realtime hand tracking using modificated flocks of fea tures algorithm information sciences and technologies bulletin of the slovakia special section on student research in inf Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview cleanTitle FINER: >>> AFTER ACM/IEEE=realtime hand tracking using modificated flocks of features algorithm realtime hand tracking using modificated flocks of fea tures algorithm information sciences and technologies bulletin of the slovakia special section on student research in inf Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview cleanTitle FINER: >>> AFTER PAGE/VOL=realtime hand tracking using modificated flocks of features algorithm realtime hand tracking using modificated flocks of fea tures algorithm information sciences and technologies bulletin of the slovakia special section on student research in inf Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview cleanTitle FINER: >>> AFTER EDs=realtime hand tracking using modificated flocks of features algorithm realtime hand tracking using modificated flocks of fea tures algorithm information sciences and technologies bulletin of the slovakia special section on student research in inf Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview cleanTitle FINER: >>> AFTER PARENTHESIS=realtime hand tracking using modificated flocks of features algorithm realtime hand tracking using modificated flocks of fea tures algorithm information sciences and technologies bulletin of the slovakia special section on student research in inf Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview cleanTitle FINER: >>> AFTER SPACING CLEAN=realtime hand tracking using modificated flocks of features algorithm realtime hand tracking using modificated flocks of fea tures algorithm information sciences and technologies bulletin of the slovakia special section on student research in inf Apr 10, 2017 10:46:33 AM fr.presans.jsofia.domain.DReview titleMatcher FINER: Found NON matching chars: a≠r [+ a lot of spaces at the end] - Opening this file with less, the ngoing up & down with arrows or pgup/pgdown, you'll notice that the lines with '>>>' will merge into a single line. See http://imgur.com/a/7ol45 I'm using: $ uname -a Linux gyom 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:51:38 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/issue Ubuntu Zesty Zapus (development branch) \n \l $ less --version less 481 (GNU regular expressions) Copyright (C) 1984-2015 Mark Nudelman I'll try the new package right now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need envi
[Touch-packages] [Bug 1679184] Re: LVM configuration cannot be removed when volume groups with the same name are found during installation
This is a won't fix bug, yes please use the provided shell or for dasd drives, use preseed to format them. You can also use partman early- command preseed to wipe the drives harder. ** Package changed: lvm2 (Ubuntu) => partman-lvm (Ubuntu) ** Changed in: partman-lvm (Ubuntu) Status: New => Won't Fix ** Changed in: ubuntu-z-systems Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1679184 Title: LVM configuration cannot be removed when volume groups with the same name are found during installation Status in Ubuntu on IBM z Systems: Won't Fix Status in partman-lvm package in Ubuntu: Won't Fix Bug description: Installer version: 20101020ubuntu500 Kernel: 4.10.0-14 Description/Reproduction: During installation, the installer finds LVM volume groups from a previous installation. Current LVM configuration: Unallocated physical volumes: * /dev/mapper/mpatha2 (21218MB) Volume groups: * rootVG (21218MB) - Uses physical volume: /dev/dasda2 (21315MB) - Uses physical volume: /dev/mapper/mpathc1 (21470MB) - Uses physical volume: [unknown](21470MB) - Uses physical volume: [unknown](21470MB) * rootVG (21470MB) - Uses physical volume: /dev/dasda2 (21315MB) - Uses physical volume: /dev/mapper/mpathc1 (21470MB) - Uses physical volume: [unknown](21470MB) - Uses physical volume: [unknown](21470MB) * rootvg (42685MB) - Uses physical volume: /dev/mapper/mpathb1 (21470MB) - Uses physical volume: [unknown](214 When trying to remove that LVM using "Configure the Logical Volume Manager", it is not possible to remove logical volumes. The error "The logical volume swapLV on rootVG could not be deleted." is displayed. In syslog, you see the following messages: Apr 3 12:55:56 partman-lvm: Multiple VGs found with the same name: skipping rootVG Apr 3 12:55:56 partman-lvm: Use --select vg_uuid= in place of the VG name. As you cannot use the suggested parameter in the installer, the system cannot be installed without manually removing the LVM setup with another shell. Debug logs are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679184/+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 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly
** Changed in: libseccomp (Ubuntu) Status: New => Confirmed ** Also affects: libseccomp (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Zesty) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Confirmed ** Also affects: libseccomp (Ubuntu Aa-series) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1679691 Title: libseccomp fix - s390: handle multiplexed syscalls correctly Status in Ubuntu on IBM z Systems: New Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Xenial: New Status in libseccomp source package in Yakkety: New Status in libseccomp source package in Zesty: Confirmed Status in libseccomp source package in aa-series: New Bug description: Within Xenial version 2.2.3 of seccomp is included. With Yaketty version 2.3.1 is available and fixed this problem. Even Docker is working on a SNAP solution, please provide the fix to 16.04. With following patches this can be applied to 2.2.3 in support of the 16.04 LTS Release 16.04 Here the upstream git commits for the patches: 0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch 1d63fad4a064b80e0b921b16ed419f3342337ed4 0001-all-block-negative-syscall-numbers-from-the-filter.patch 51c46f80c1edee863bbc4eb21b03decc44e69a45 0001-api-limit-errno-values-to-MAX_ERRNO.patch 0d287caf43792239b107ee3215b32b8bc901f9c3 0001-db-fix-a-minor-style-problem.patch 61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 0001-db-make-the-individual-db-filter-ops-private.patch a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16 0001-db-store-the-rules-used-to-build-the-filter.patch f16f405f61ecdbad202257b61004b85fce64d75c 0001-arch-make-use-of-function-tables-instead-of-switch-s.patch 57df79c166b26d5044e7e27099e6e69671e727dd 0001-db-introduce-transaction-support.patch 9be1538a4ac0e45047a3f1b79691505c3d11ca31 0001-arch-move-the-low-level-filter-rule-addition-code-in.patch 996e445a74823c735757413fda809e1ed0afc7d4 0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch 5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 0001-arch-basic-support-for-multiplexed-and-direct-socket.patch d32c3bfa4b07add90dcd04292eb4ba278dd103ba 0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch 983835f3e0fd000a42c8beaea9d7fbe72665 0001-tests-add-a-test-for-the-different-types-of-socket-s.patch 099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 0001-api-add-a-seccomp_version-API-call.patch 58a7c20d4c2defc1c984c5c7391ecc60093f85fa 0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch 8ed78c3859f476d302995b43d6739f3341f5b37d 0001-s390-handle-multiplexed-syscalls-correctly.patch 47516603828396f85107ea3e2a254958c2bc3ff5 0001-arch-fix-the-multiplexed-ipc-syscalls.patch 3a89bd144885f54aff86f2e275859a1483992edd With the following additional commit all tests pass with "make check" 0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch 0d8504bc192e0989494df06efc4b186a9f02e20a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679691/+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 1679674] Re: s390x: Interface order in kvm guest image not predictable
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.04 ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1679674 Title: s390x: Interface order in kvm guest image not predictable Status in systemd package in Ubuntu: Confirmed Bug description: ---Problem Description--- Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest is launched with 2 network interfaces connected to 2 different open vswitch bridges. The problem is 2-fold: #1 In the guest it seems like that the interface order is not predicitve. Device names used are eth0, eth1. The device that is listed first in libvirts domain.xml is not necessarily eth0. #2 The device names are not persistet. On the next boot eth0 might be eth1 and vice verca. Contact Information = andreas.scheur...@de.ibm.com ---uname output--- Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 s390x s390x s390x GNU/Linux Machine Type = KVM guest ---Debugger--- A debugger is not configured ---Steps to Reproduce--- guest Domain xml: Ubuntu16VM 455e6998-cec1-4010-99a6-d033ee6d3385 524288 524288 2 /machine hvm destroy restart preserve /usr/bin/qemu-system-s390x libvirt-455e6998-cec1-4010-99a6-d033ee6d3385 libvirt-455e6998-cec1-4010-99a6-d033ee6d3385 in the guest check interfaces and remember the mac address # ip a Do a reboot (or multiple) and check again if the interface-mac combination is still the same The interface order should change from time to time Userspace tool common name: udev? Userspace rpm: ? The userspace tool has the following bit modes: 64 Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679674/+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 1410012] Re: Does not detect hotplugged storage device
As far as I understand big hard-drives are not automatically mounted - but should be present as partitions to mount via nautilus. E.g. I would not expect 4TiB drives to automount. Automatically mounted are only flash-usb sticks. -- 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/1410012 Title: Does not detect hotplugged storage device Status in systemd package in Ubuntu: New Bug description: I plug it in, it doesn't automatically mount, is not visible in nautilus. Mounts fine on system start up. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 218-3ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 12 22:07:54 2015 EcryptfsInUse: Yes HotplugNewDevices: /dev/sda /dev/sda1 HotplugNewMounts: InstallationDate: Installed on 2014-07-09 (187 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) MachineType: Acer TravelMate P273-MG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-8-generic root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate P273-MG dmi.product.version: V2.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1410012/+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 1680597] Re: udev 60-block.rules does not watch bcache
** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.04 -- 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/1680597 Title: udev 60-block.rules does not watch bcache Status in systemd package in Ubuntu: Confirmed Bug description: bcache devices do not have a watch on them from /lib/udev/rules.d/60-block.rules The result is that this will fail: mkfs.ext4 /dev/bcache0 -L foobar udevadm settle ls -l /dev/disk/by-label/foobar where as it will work on mkfs.ext4 /dev/vdb -L foobar udevadm settle ls -l /dev/disk/by-label/foobar We found this when chasing a curtin bug (bug 1680591). The result of it was that we were installing and an update-grub would choose to boot with root=/dev/bcache0 rather than UUID=. Related bugs: * bug 1680591: installed system boots with root=/dev/bcache0 rather than root=UUID when root is bcache ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-19 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Apr 6 16:28:59 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (623 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1680597/+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 1681346] Re: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/1681346 Title: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in eject package in Ubuntu: New Bug description: After start up the system error report pops up. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 9 10:12:02 2017 DuplicateSignature: package:eject:2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 Processing triggers for libc-bin (2.23-0ubuntu7) ... dpkg: error processing package eject (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-04-26 (348 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: eject Title: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1681346/+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