[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
Major categorization aspects: - this very important core functionality (properly reliable resource management of DHCP leases, also in suspend-to-RAM etc.) **NEVER EVER WORKS** (exclusively suspend-to-RAM use case here, ending up with stale IP address): - this did not work in 12.04LTS - this still did not work after upgrade to 14.04LTS - this STILL did not work after upgrade to 16.04LTS (recently upgraded, i.e. after activity of #12 which says that it DID work there, yet perhaps not suspend-to-RAM) - importance of this bug should be "a lot higher than High" Justification: - messes with/breaks (CORRUPTS!!) environment even *beyond* local system scope (--> inacceptable!!), due to continuing communication via a stale IP address which has long since been re-assigned to other hosts (as can be verified via DNS query) - has been observed in *all* recent LTS releases (which are expected to work fine in large enterpriseish environments??) --> Ubuntu release process is sorely missing reliable verification (persistently executed test case) for this core functionality, to ensure that this is (and keeps!) not causing damage, at least in production (stable) distributions Example to achieve fixing stale IP (renew DHCP lease): nmcli c nmcli c down uuid nmcli c up uuid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in bind9 package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in bind9 source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"
Not fully successfully fixed via comment #18: $ sudo gdk-pixbuf-query-loaders | tee /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache tee: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied Thus should instead do entire execution chain via an admin shell (e.g.: sudo -s) proper. Also prefer using (pasting) the unmodified since original suggestion in installation log (due to other potential deviations such as architecture-specific i386 vs. x86_64 paths). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539046] Re: libGL error: failed to open drm device: Permission denied
Encountered very similar things (error message usability issue). --> filed improvement suggestion at https://bugs.freedesktop.org/show_bug.cgi?id=98163 ** Bug watch added: freedesktop.org Bugzilla #98163 https://bugs.freedesktop.org/show_bug.cgi?id=98163 -- 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/1539046 Title: libGL error: failed to open drm device: Permission denied Status in xorg package in Ubuntu: New Bug description: After some update (unfortunately I'm not sure what) if I try to play a videofile (e.g. mpv movie.mkv) I get this error: libGL error: failed to open drm device: Permission denied I think from this message is not very clear why is that. I figured out I was not in "video" group: "id user_name" I had to do this: "usermod -aG video user_name " and then restart X (logout, login). After that it works again. So I suspect there is some problem there. Why libGL cannot be used without membership in video group or why a regular user is not in video group. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 28 12:54:51 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-25-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2248] InstallationDate: Installed on 2015-10-23 (96 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP ProBook 450 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic root=UUID=c9e0c6ee-c8a4-4d1a-a46e-a3b79c38f774 ro SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.16 dmi.board.name: 2248 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.16:bd11/26/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3008CD10003:rvnHewlett-Packard:rn2248:rvrKBCVersion67.24:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 450 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A 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.11-1ubuntu3 xserver.bootTime: Wed Jan 27 22:49:34 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1125 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1539046/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: Ubuntu should have an upstart job for saving/restoring backlight level on laptops
Commenting on #18: Checking the brightness script (POSIX-incompatible bashisms etc.), my system says: # checkbashisms brightness possible bashism in brightness line 30 (unsafe echo with backslash): echo \tloading $saved_controller_name possible bashism in brightness line 40 (unsafe echo with backslash): echo \tsaving $controller_name possible bashism in brightness line 50 (unsafe echo with backslash): echo \tCurrent brightness level for $controller_name is $(cat $controller/brightness) possible bashism in brightness line 58 (unsafe echo with backslash): echo \tSaved brightness level for $saved_controller_name is $(cat $saved_file) (should probably prefer using the printf helper for that, since a \t control code might possibly require echo -e, yet availability of sufficiently compatible echo -e possibly isn't guaranteed) Also some variable uses are not -quoted, which will cause issues in case of space-containing filesystem items (which is somewhat unlikely to be encountered in the case of firmly Linux-managed /proc or /sys entries, but still...). And some path strings are openly duplicated rather than assigned to helper variables. All in all these are fairly minor issues, and I didn't runtime test the script anyway. I simply decided to be bored enough to do a code review ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: Ubuntu should have an upstart job for saving/restoring backlight level on laptops Status in elementary OS: Confirmed Status in One Hundred Papercuts: Confirmed Status in Ubuntu MATE: Opinion Status in systemd package in Ubuntu: Triaged Status in sysvinit package in Ubuntu: Confirmed Status in sysvinit package in Debian: New Bug description: I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7, Sabayon, Mageia 4. Many of them are based on systemd. It does not matter what init system they use, but all of them have very usefull script (or binary program, I don't know) for saving and restoring backlight level on laptop. In these distros there is a script for save and restore backlight levels for two video-cards (acpi_video0 and acpi_video1). During system boot it is indicated as follows: [ OK ] Started Load/Save Screen Backlight Brightness of acpi_video1. [ OK ] Started Load/Save Screen Backlight Brightness of acpi_video0. . I have a draft version, which works normally on my VAIO F13Z1R laptop with Ubuntu 12.04.4. It is in attachment. You can use it unmodified or modify it for compatibility or something. I made symlinks for it: ln -s /etc/init.d/brightness /etc/rc0.d/S25backlight ln -s /etc/init.d/brightness /etc/rcS.d/S25backlight ln -s /etc/init.d/brightness /etc/rc6.d/S25backlight For details you can read my comment on askubuntu (http://askubuntu.com/a/227553/66509). I think that having a script for saving and restoring backlight level is very useful for laptop Ubuntu users. So, please, add such init script to default Ubuntu installation. 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/elementaryos/+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
