[Bug 1673591] [NEW] PyGIWarning: Gtk was imported without specifying a version first.
Public bug reported:
On Ubuntu 16.04.2 with smart-notifier 0.28-5, the following warning is
output to the terminal on launch:
% smart-notifier
/usr/share/smart-notifier/smart_notifier/gui.py:23: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
A test of smart-notifier like:
% echo test | sudo smart-notifier --notify
showed that it is working. So apparently just a warning.
This is similar to bug #1598896, but the details are a bit different.
** Affects: smart-notifier (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673591
Title:
PyGIWarning: Gtk was imported without specifying a version first.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smart-notifier/+bug/1673591/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603988] Re: twinkle terminate called after throwing an instance of 'std::logic_error'
I saw an app report dialog pointing to the failure that I believe is referenced in bug 1631210. Then when trying to launch from the command line I see: % twinkle Language name: "en" terminate called after throwing an instance of 'std::logic_error' what(): Mutex lock failed Abort (core dumped) This started happening on a 16.04 system after installing an update that included the following packages: accountsservice (0.6.40-2ubuntu11.3) apt-transport-https (1.2.15) apt-utils (1.2.15) cinnamon (3.2.1-1~xenial0) cinnamon-common (3.2.1-1~xenial0) cinnamon-control-center (3.2.0-1~xenial0) cinnamon-control-center-data (3.2.0-1~xenial0) cinnamon-desktop-data (3.2.0-1~xenial0) cinnamon-l10n (3.2.1-1~xenial0) cinnamon-screensaver (3.2.3-1~xenial0) cinnamon-session (3.2.0-1~xenial0) cinnamon-session-common (3.2.0-1~xenial0) cinnamon-settings-daemon (3.2.0-1~xenial0) cjs (3.2.0-1~xenial0) fonts-lato (2.0-1) gawk (1:4.1.3+dfsg-0.1) gir1.2-accountsservice-1.0 (0.6.40-2ubuntu11.3) gir1.2-cinnamondesktop-3.0 (3.2.0-1~xenial0) gir1.2-cmenu-3.0 (3.2.0-1~xenial0) gir1.2-cvc-1.0 (3.2.0-1~xenial0) gir1.2-meta-muffin-0.0 (3.2.0-1~xenial0) gir1.2-xapp-1.0 (1.0.2-1~xenial1) gist (4.5.0-2) hddtemp (0.3-beta15-52) inxi (2.2.35-0ubuntu1) isc-dhcp-client (4.3.3-5ubuntu12.4) isc-dhcp-common (4.3.3-5ubuntu12.4) iso-flag-png (1.0.0-1~xenial0) javascript-common (11) libaccountsservice0:amd64 (0.6.40-2ubuntu11.3) libapt-inst2.0:amd64 (1.2.15) libcinnamon-control-center1:amd64 (3.2.0-1~xenial0) libcinnamon-desktop4:amd64 (3.2.0-1~xenial0) libcinnamon-menu-3-0 (3.2.0-1~xenial0) libcjs0e (3.2.0-1~xenial0) libcscreensaver0:amd64 (3.2.3-1~xenial0) libcvc0:amd64 (3.2.0-1~xenial0) libfcitx-config4:amd64 (1:4.2.9.1-1ubuntu1.16.04.1) libfcitx-gclient0:amd64 (1:4.2.9.1-1ubuntu1.16.04.1) libfcitx-utils0:amd64 (1:4.2.9.1-1ubuntu1.16.04.1) libjs-jquery (1.11.3+dfsg-4) libmuffin0 (3.2.0-1~xenial0) libnemo-extension1 (3.2.0-1~xenial0) libprocps4:amd64 (2:3.3.10-4ubuntu2.2) libruby2.3:amd64 (2.3.1-2~16.04) libxapp1:amd64 (1.0.2-1~xenial1) linux-firmware (1.157.5) lm-sensors (1:3.4.0-2) muffin-common (3.2.0-1~xenial0) nemo (3.2.0-1~xenial0) nemo-data (3.2.0-1~xenial0) nemo-fileroller (3.2.0-1~xenial0) procps (2:3.3.10-4ubuntu2.2) python3-distupgrade (1:16.04.18) python3-xlib (0.14+20091101-5) rake (10.5.0-2) ruby (1:2.3.0+1) ruby2.3 (2.3.1-2~16.04) ruby-did-you-mean (1.0.0-2) rubygems-integration (1.10) ruby-json (1.8.3-1build4) ruby-minitest (5.8.4-2) ruby-net-telnet (0.1.1-2) ruby-power-assert (0.2.7-1) ruby-test-unit (3.1.7-2) ubuntu-release-upgrader-core (1:16.04.18) ubuntu-release-upgrader-gtk (1:16.04.18) unattended-upgrades (0.90ubuntu0.2) xapps-common (1.0.2-1~xenial1) xserver-common (2:1.18.4-0ubuntu0.2) xserver-xorg-core (2:1.18.4-0ubuntu0.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603988 Title: twinkle terminate called after throwing an instance of 'std::logic_error' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1603988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872824] Re: Network-manager locks up when adding strongSwan VPN connection
Here are the steps to install the 12.10 binaries on 12.04: % wget http://launchpadlibrarian.net/108979339/network-manager-strongswan_1.3.0-0ubuntu1_amd64.deb % wget http://launchpadlibrarian.net/108979332/strongswan-nm_4.5.2-1.5ubuntu2_amd64.deb % wget http://launchpadlibrarian.net/108979331/strongswan-ikev2_4.5.2-1.5ubuntu2_amd64.deb % wget http://launchpadlibrarian.net/108979327/libstrongswan_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i libstrongswan_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i strongswan-ikev2_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i strongswan-nm_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i network-manager-strongswan_1.3.0-0ubuntu1_amd64.deb I can confirm this gets you past the hang and lets the config dialog appear. I can't confirm that strongswan itself is functional, as the other end of the connection I'm testing requires a pre-shared key, and the strongswan wiki[1] page on the Network Manager plugin notes that, PSK is not supported, as it is considered insecure if the secrets are not strong enough. (So PSK is supported by strongswan (as documented elsewhere), just not by the Network Manager plugin. Thanks for the value judgment.) 1. http://wiki.strongswan.org/projects/strongswan/wiki/NetworkManager Reinstalling openswan. -Tom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/872824 Title: Network-manager locks up when adding strongSwan VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/872824/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 872824] Re: Network-manager locks up when adding strongSwan VPN connection
Here are the steps to install the 12.10 binaries on 12.04: % wget http://launchpadlibrarian.net/108979339/network-manager-strongswan_1.3.0-0ubuntu1_amd64.deb % wget http://launchpadlibrarian.net/108979332/strongswan-nm_4.5.2-1.5ubuntu2_amd64.deb % wget http://launchpadlibrarian.net/108979331/strongswan-ikev2_4.5.2-1.5ubuntu2_amd64.deb % wget http://launchpadlibrarian.net/108979327/libstrongswan_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i libstrongswan_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i strongswan-ikev2_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i strongswan-nm_4.5.2-1.5ubuntu2_amd64.deb % sudo dpkg -i network-manager-strongswan_1.3.0-0ubuntu1_amd64.deb I can confirm this gets you past the hang and lets the config dialog appear. I can't confirm that strongswan itself is functional, as the other end of the connection I'm testing requires a pre-shared key, and the strongswan wiki[1] page on the Network Manager plugin notes that, PSK is not supported, as it is considered insecure if the secrets are not strong enough. (So PSK is supported by strongswan (as documented elsewhere), just not by the Network Manager plugin. Thanks for the value judgment.) 1. http://wiki.strongswan.org/projects/strongswan/wiki/NetworkManager Reinstalling openswan. -Tom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872824 Title: Network-manager locks up when adding strongSwan VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/872824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Re: delay: estimated N, actual N warning logged by kernel
Have you tried a different USB port(s)? Yes. I plugged the USB sound adapter into a different port and the logged warnings persisted. The laptop has 1 through 8 USB buses listed by lsusb, but only 3 external ports. Currently (and originally) attached as: Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter I temporarily tried it on: Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub which has two ports. I didn't bother trying it on both ports of that hub. Here's the full device list (probably redundant with one of the attachments above): Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 005: ID 064e:a117 Suyin Corp. (webcam) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 138a:0001 Validity Sensors, Inc. VFS101 Fingerprint Reader Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver (mouse) Bus 006 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] [NEW] delay: estimated N, actual N warning logged by kernel
Public bug reported: A recent Ubuntu 12.04 update has resulted in a flood of kernel log messages like: Jun 10 16:53:50 fringe kernel: [1083938.675908] delay: estimated 222, actual 1 Jun 10 16:53:53 fringe kernel: [1083941.451942] delay: estimated 89, actual 0 Jun 10 16:54:02 fringe kernel: [1083950.876085] delay: estimated 309, actual 1 Jun 10 16:54:12 fringe kernel: [1083961.212252] delay: estimated 266, actual 1 Jun 10 16:54:28 fringe kernel: [1083976.940540] delay: estimated 265, actual 0 Jun 10 16:54:31 fringe kernel: [1083979.444548] delay: estimated 177, actual 1 Jun 10 16:54:40 fringe kernel: [1083989.164726] delay: estimated 265, actual 1 Jun 10 16:54:48 fringe kernel: [1083997.216594] delay: estimated 354, actual 1 Jun 10 16:54:48 fringe kernel: [1083997.220835] delay: estimated 134, actual 1 Jun 10 16:54:55 fringe kernel: [1084003.572938] delay: estimated 222, actual 1 Jun 10 16:55:31 fringe kernel: [1084039.821516] delay: estimated 266, actual 1 Jun 10 16:55:33 fringe kernel: [1084041.717585] delay: estimated 89, actual 0 whenever a USB sound card is used. (Even just sitting idle with no playback. As long as the card is selected as the output device in Sound settings, it happens.) Here's a link to a message from about a year ago where Pierre-Louis Bossart says he is the one who added this diagnostic message: http://permalink.gmane.org/gmane.linux.alsa.devel/97011 Other references include: https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=798844 http://www.gossamer-threads.com/lists/linux/kernel/1592033?do=post_view_threaded There appears to be no functional impact or difference compared to how the sound card worked prior to the update. The warnings are either in error or warning of an insignificant condition. The main problem with them is that they obscure important errors in the kernel logs, and waste disk space. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Card1.Amixer.values.txt
apport information ** Attachment added: Card1.Amixer.values.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700341/+files/Card1.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700336/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Card0.Codecs.codec.1.txt
apport information ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700339/+files/Card0.Codecs.codec.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700334/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Card0.Codecs.codec.2.txt
apport information ** Attachment added: Card0.Codecs.codec.2.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700340/+files/Card0.Codecs.codec.2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Re: delay: estimated N, actual N warning logged by kernel
apport information ** Tags added: apport-collected precise ** Description changed: A recent Ubuntu 12.04 update has resulted in a flood of kernel log messages like: Jun 10 16:53:50 fringe kernel: [1083938.675908] delay: estimated 222, actual 1 Jun 10 16:53:53 fringe kernel: [1083941.451942] delay: estimated 89, actual 0 Jun 10 16:54:02 fringe kernel: [1083950.876085] delay: estimated 309, actual 1 Jun 10 16:54:12 fringe kernel: [1083961.212252] delay: estimated 266, actual 1 Jun 10 16:54:28 fringe kernel: [1083976.940540] delay: estimated 265, actual 0 Jun 10 16:54:31 fringe kernel: [1083979.444548] delay: estimated 177, actual 1 Jun 10 16:54:40 fringe kernel: [1083989.164726] delay: estimated 265, actual 1 Jun 10 16:54:48 fringe kernel: [1083997.216594] delay: estimated 354, actual 1 Jun 10 16:54:48 fringe kernel: [1083997.220835] delay: estimated 134, actual 1 Jun 10 16:54:55 fringe kernel: [1084003.572938] delay: estimated 222, actual 1 Jun 10 16:55:31 fringe kernel: [1084039.821516] delay: estimated 266, actual 1 Jun 10 16:55:33 fringe kernel: [1084041.717585] delay: estimated 89, actual 0 whenever a USB sound card is used. (Even just sitting idle with no playback. As long as the card is selected as the output device in Sound settings, it happens.) Here's a link to a message from about a year ago where Pierre-Louis Bossart says he is the one who added this diagnostic message: http://permalink.gmane.org/gmane.linux.alsa.devel/97011 Other references include: https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=798844 http://www.gossamer-threads.com/lists/linux/kernel/1592033?do=post_view_threaded There appears to be no functional impact or difference compared to how the sound card worked prior to the update. The warnings are either in error or warning of an insignificant condition. - The main problem with them is that they obscure important errors in the - kernel logs, and waste disk space. + The main problem with them is that they obscure important errors in the kernel logs, and waste disk space. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 2.0.1-0ubuntu17.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tmetro 2686 F pulseaudio + /dev/snd/pcmC0D0p: tmetro 2686 F...m pulseaudio + /dev/snd/controlC1: tmetro 2686 F pulseaudio + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xdb30 irq 47' +Mixer name : 'Nvidia MCP77/78 HDMI' +Components : 'HDA:10ec0889,10250145,0014 HDA:11c11040,10250145,00100200 HDA:10de0006,10de0101,0010' +Controls : 38 +Simple ctrls : 21 + Card1.Amixer.info: + Card hw:1 'Set'/'C-Media USB Headphone Set at usb-:00:1d.0-2, full speed' +Mixer name : 'USB Mixer' +Components : 'USB0d8c:000c' +Controls : 5 +Simple ctrls : 3 + CheckboxSubmission: 4a2fa194ac4b2025b572a728c22df868 + CheckboxSystem: ed86e29ffba809c116a39e33fa9fc45c + DistroRelease: Ubuntu 12.04 + EcryptfsInUse: Yes + InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) + MarkForUpload: True + Package: alsa-driver (not installed) + ProcVersionSignature: Ubuntu 3.2.0-44.69-generic 3.2.44 + Tags: precise + Uname: Linux 3.2.0-44-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirtd lpadmin mythtv plugdev sambashare sudo + dmi.bios.date: 09/09/2008 + dmi.bios.vendor: Acer + dmi.bios.version: V1.06 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: Aspire 8930 + dmi.board.vendor: Acer + dmi.board.version: PSMBOU-1234567 + dmi.chassis.type: 1 + dmi.chassis.vendor: Acer + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAcer:bvrV1.06:bd09/09/2008:svnAcer:pnAspire8930:pvrV1.06:rvnAcer:rnAspire8930:rvrPSMBOU-1234567:cvnAcer:ct1:cvrN/A: + dmi.product.name: Aspire 8930 + dmi.product.version: V1.06 + dmi.sys.vendor: Acer ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700333/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700337/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700338/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700335/+files/ArecordDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700343/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700346/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700345/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700344/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189661] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1189661/+attachment/3700347/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189661 Title: delay: estimated N, actual N warning logged by kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1189661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187144] [NEW] package deluge for headless operation
Public bug reported: I installed deluged, deluge-web, and deluge-console and followed the headless setup instructions here: http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient expecting that most of the described steps would have been done for me by the Ubuntu packaging, but discovered they had not. My conclusion is that Deluge is packaged for the more typical user running a combined client-server setup on a local machine. Thus deluged doesn't auto-start, for example, because it is assumed the typical user will have it start on demand when the GUI starts. It should be easier to get a headless setup going. Traditionally I'd say the deluged package should prompt the user on install to select the mode, but my understanding is that interactive prompting at package install time is discouraged. Besides, for a useful headless install, it seems you really need deluge-console (to manage some of the config settings) and deluge-web (even if you don't need a web UI, some 3rd party Deluge clients use the JSON API it provides). My recommendation is that: 1. fix the issues described in Bug #1096267 so the deluged and deluge- web packages are up to modern standards. 2. figure out whether the deluge-web package should behave like a plugin for the GUI (if you install the web UI from within he GUI, does it even use this package?) or as a standard service package with appropriate startup scripts. 3. create a deluge-headless package that depends on deluged, deluge- web, and deluge-console, and reconfigures them to run as services and start automatically. It should also include a SetUID wrapper (or similar) for deluge-console, so it can be used to manage deluged running as the deluge user (whatever the deluged package uses). (Perhaps, if the package properly configures deluged, there will be no need for deluge- console, and it can be eliminated from the deluge-headless dependencies. I'm too new to Deluge to know if deluge-console is ever needed after you've enabled remote access. Can deluged be fully administered from the GUI client thereafter?) deluge-headless may still require a prompt at installation time to create login credentials for a remote user, as creating a default one is probably discouraged. The setup guide above suggests modifying the auth file directly to do this, which seems to imply ths is not something deluge-console can do. It would seem a fairly trivial script (deluge- user) could be included in the package to manage the auth file. In theory a working headless Deluge setup should be accomplished with something like: % sudo aptitude install deluge-headless % sudo deluge-user --add --user remote_user --pass remote_pass --level admin % ssh otherhost otherhost% deluge-console connect deluge_server remote_user remote_pass Connected to deluge_server:58846 (deluge-user could support a simple interactive mode, where running it without arguments would dump the current list of users in the auth file, and give you options to delete/modify them, or add a new user. This way the user doesn't need to learn the command line syntax of a tool they'll rarely ever use. The only remaining challenge is making sure users know they need to run deluge-user post install.) ** Affects: deluge (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187144 Title: package deluge for headless operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/1187144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096267] Re: Please provide an upstart job
Please provide an upstart job I'm going to redundantly echo that sentiment. As noted above the upstream project provides the necessary scripts. I think the issues in this bug exist largely because the packaging wasn't intended to support headless users, as I speculated in Bug #1187144. Also, deluge-web is also missing an upstart job, as a matter of fact, it doesn't have an init script either. Again, I'm wondering is this package was created with the assumption that the user would be launching it from the GUI. Otherwise, you'd have to consider the package broken, as it is incomplete with respect to being an Ubuntu service package. Also, why not use the name 'deluge' or 'deluged' as the username/groupname instead of debian-deluged? Obviously carried over from Debian packaging. I'd be curious to know why the Debian packager felt it was necessary to add the prefix. Did he get complaints of name conflicts? In any case, it sounds like with a few fairly trivial tweaks these packages could be modernized, and combined with a bit of glue, as I describe in Bug #1187144 to create a fairly painless headless install experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096267 Title: Please provide an upstart job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/1096267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156460] [NEW] p7zip-full claims to include p7zip command, but does not
Public bug reported: % aptitude show p7zip-full Package: p7zip-full Version: 9.20.1~dfsg.1-4 [...] p7zip provides 7zr, a light version of 7za, and p7zip, a gzip-like wrapper around 7zr. % dpkg -c /var/cache/apt/archives/p7zip-full_9.20.1~dfsg.1-4_amd64.deb drwxr-xr-x root/root 0 2012-02-17 15:08 ./ drwxr-xr-x root/root 0 2012-02-17 15:08 ./usr/ drwxr-xr-x root/root 0 2012-02-17 15:08 ./usr/bin/ -rwxr-xr-x root/root39 2012-02-17 15:01 ./usr/bin/7z -rwxr-xr-x root/root40 2012-02-17 15:01 ./usr/bin/7za drwxr-xr-x root/root 0 2012-02-17 15:08 ./usr/lib/ [...] p7zip is missing. ** Affects: p7zip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156460 Title: p7zip-full claims to include p7zip command, but does not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p7zip/+bug/1156460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156460] Re: p7zip-full claims to include p7zip command, but does not
As a workaround I extracted the wrapper script from the non-full
package:
% cd /tmp
% wget http://launchpadlibrarian.net/93194080/p7zip_9.20.1%7Edfsg.1-4_amd64.deb
% mkdir p7zip_9.20.1%7Edfsg.1-4_amd64
% dpkg-deb -x p7zip_9.20.1~dfsg.1-4_amd64.deb p7zip_9.20.1~dfsg.1-4_amd64
% sudo cp p7zip_9.20.1~dfsg.1-4_amd64/usr/bin/p7zip /usr/local/bin/
% sudo mkdir /usr/locl/man/man1
% sudo cp p7zip_9.20.1~dfsg.1-4_amd64/usr/share/man/man1/p7zip.1.gz
/usr/local/man/man1/
Then I patched the script to s/7zr/7za/ for compatibility with p7zip-
full:
diff -u -r1.1 -r1.4
--- p7zip 2013/03/18 06:21:07 1.1
+++ p7zip 2013/03/18 06:29:49 1.4
@@ -32,7 +32,7 @@
done
# make sure they're present, before we screw up
-for i in mktemp 7zr rm cat tty ; do
+for i in mktemp 7za rm cat tty ; do
if ! which $i /dev/null ; then
echo $0: $i: command not found
exit 1
@@ -41,12 +41,12 @@
if [ ${file} != ] ; then
if ${compress} ; then
-7zr a ${file}.7z ${file}
+7za a ${file}.7z ${file}
exec rm ${file}
else
case ${file} in
*.7z)
-7zr x ${file}
+7za x ${file}
exec rm ${file}
;;
*)
@@ -67,11 +67,11 @@
exit 1
fi
rm -f ${tmp}
- 7zr a ${tmp} -si /dev/null
+ 7za a ${tmp} -si /dev/null
cat ${tmp}
else
cat ${tmp}
- 7zr x ${tmp} -so 2/dev/null | cat
+ 7za x ${tmp} -so 2/dev/null | cat
fi
exec rm -f ${tmp}
This:
% perl -i -e 's/7zr/7za/' /usr/local/bin/p7zip
should do the same as above, if you prefer not to use 'patch'.
I also created:
/usr/local/bin% ln -s /usr/bin/7za 7zip
/usr/local/bin% ln -s p7zip 7zip-pipe
because I find p7zip and 7za to be unintuitive names for a tool known as 7-zip.
It doesn't help that:
man -k 7zip
man -k zip
doesn't turn up any of these commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156460
Title:
p7zip-full claims to include p7zip command, but does not
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/p7zip/+bug/1156460/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155398] [NEW] MIME types are not registered
Public bug reported: Installed 2.0-426-gc32b3ed-2ubuntu0.1 on Ubuntu 12.04.1. GUI file managers, such as Nautilus, were unaware of the existence of mplayer because it does not install the necessary .desktop files to associate it with the MIME types it can handle. Seems like this should be part of the packaging for Ubuntu. Work-around: follow the procedure here: http://askubuntu.com/questions/67382/add-custom-command-in-the-open-with-dialog to manually create the associations. ** Affects: mplayer2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155398 Title: MIME types are not registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer2/+bug/1155398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076461] Re: unmatched entries for smartd
Also: smartd 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-33-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Device: /dev/sda [SAT], ST95005620AS, S/N:5YX12P01, WWN:5-000c50-038cde7d2, FW:SD26, 500 GB Device: /dev/sdb [SAT], WDC WD3200BEKT-22F3T0, S/N:WD-WXM908SJ1447, WWN:5-0014ee-2023443ed, FW:11.01A11, 320 GB -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1076461 Title: unmatched entries for smartd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1076461/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076461] Re: unmatched entries for smartd
Also: smartd 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-33-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Device: /dev/sda [SAT], ST95005620AS, S/N:5YX12P01, WWN:5-000c50-038cde7d2, FW:SD26, 500 GB Device: /dev/sdb [SAT], WDC WD3200BEKT-22F3T0, S/N:WD-WXM908SJ1447, WWN:5-0014ee-2023443ed, FW:11.01A11, 320 GB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076461 Title: unmatched entries for smartd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1076461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076464] [NEW] unmatched entries for gnome-screensaver
Public bug reported: logwatch 7.4.0+svn20111221rev79-1ubuntu1 on Ubuntu 12.04.1 I am running Cinnamon desktop, which might impact the presence of this message, but that seems unlikely, as gnome-screensaver is common to several desktops. **Unmatched Entries** gnome-screensaver-dialog: gkr-pam: unlocked login keyring: 2 Time(s) ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1076464 Title: unmatched entries for gnome-screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1076464/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076461] [NEW] unmatched entries for smartd
Public bug reported: logwatch 7.4.0+svn20111221rev79-1ubuntu1 on Ubuntu 12.04.1 These all look like pretty mundane, non-error entries that should be filtered out: **Unmatched Entries** Device: /dev/sdb [SAT], offline data collection was suspended by an interrupting command from host (auto:on) Device: /dev/sda [SAT], previous self-test was interrupted by the host with a reset Device: /dev/sdb [SAT], offline data collection was completed without error (auto:on) Device: /dev/sdb [SAT], offline data collection was suspended by an interrupting command from host (auto:on) Device: /dev/sdb [SAT], offline data collection was completed without error (auto:on) ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1076461 Title: unmatched entries for smartd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1076461/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076464] [NEW] unmatched entries for gnome-screensaver
Public bug reported: logwatch 7.4.0+svn20111221rev79-1ubuntu1 on Ubuntu 12.04.1 I am running Cinnamon desktop, which might impact the presence of this message, but that seems unlikely, as gnome-screensaver is common to several desktops. **Unmatched Entries** gnome-screensaver-dialog: gkr-pam: unlocked login keyring: 2 Time(s) ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076464 Title: unmatched entries for gnome-screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1076464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076461] [NEW] unmatched entries for smartd
Public bug reported: logwatch 7.4.0+svn20111221rev79-1ubuntu1 on Ubuntu 12.04.1 These all look like pretty mundane, non-error entries that should be filtered out: **Unmatched Entries** Device: /dev/sdb [SAT], offline data collection was suspended by an interrupting command from host (auto:on) Device: /dev/sda [SAT], previous self-test was interrupted by the host with a reset Device: /dev/sdb [SAT], offline data collection was completed without error (auto:on) Device: /dev/sdb [SAT], offline data collection was suspended by an interrupting command from host (auto:on) Device: /dev/sdb [SAT], offline data collection was completed without error (auto:on) ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076461 Title: unmatched entries for smartd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1076461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876105] Re: Remote Desktop Viewer (vinagre) does not remember passwords
Also seen in vinagre 3.4.2 in Ubuntu 12.04.1 (64-bit) running under Cinnamon desktop. Added link to upstream bug. ** Bug watch added: GNOME Bug Tracker #658441 https://bugzilla.gnome.org/show_bug.cgi?id=658441 ** Also affects: vinagre via https://bugzilla.gnome.org/show_bug.cgi?id=658441 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876105 Title: Remote Desktop Viewer (vinagre) does not remember passwords To manage notifications about this bug go to: https://bugs.launchpad.net/vinagre/+bug/876105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 731552] Re: [wishlist] create a to read queue or a way to save specific messages
Another way to go on this would be Read It Later/Pocket/Instapaper/and similar service integration. It would need some config UI to set up an article saving service. Thereafter you can right-click on a link and select Add to [service] from the context manu. Perhaps even declaring a shortcut key that will modift a normal link click to use a service instad of opening a browser. An option to set the defaut click response to use a chosen service would also be helpful. (Whether Gwibber takes responsibility for resolving redirects before handing it to the service is a question that would need to be resolved. Some services may already handle this.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/731552 Title: [wishlist] create a to read queue or a way to save specific messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/731552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113061] Re: gnotime crashes when out of disk space
Using 2.3.1~snapshot20090531-1ubuntu2 on Ubuntu 9.10. I've had out of disk space issues with GnoTime before, but they were always easily resolved by replacing the main data file with a backup. This time I kept getting the Cannot open the project data file Shall I setup a new configuration? error dialog even though the file was clearly there, and strace showed it wasn't even attempting to access .gnome2/gnotime.d/gnotime-data.xml. Answering yes in the dialog just led to a seg fault (apparently in the midst of processing socket I/O with the X server). After an hour of troubleshooting, the problem was finally resolved by reinstalling the package: % sudo aptitude reinstall gnotime -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/113061 Title: gnotime crashes when out of disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnotime/+bug/113061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 402233] Re: [wishlist] Follow twitter user + Display 'bio', website', ... on UserPage (when clicking on a @username)
add a follow (+) icon under usernames This bug addresses this: https://bugs.launchpad.net/gwibber/+bug/519262 (Though not necessarily with the same UI. Post your UI suggestions for following there.) why not add more info like bio, website, location I recommend editing the title of this bug to focus on this aspect of the suggestion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/402233 Title: [wishlist] Follow twitter user + Display 'bio', website', ... on UserPage (when clicking on a @username) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477891] Re: keepassx don't copy the password into buffer by pressing Ctrl+C
Farfurkis wrote: To fix the bug you must simply move the USA keyboard layout to the top of layouts list... This does not resolve the problem for me. The USA keyboard layout was already at the top of the list. Besides, that thread describes a problem with shortcut keystrokes. This bug is more fundamental to keepassx and impacts the functionality of the content menus as well. Once the bug is triggered, there is no way to get data out of keepassx, short of a reboot, or using the auto-type feature. -Tom -- keepassx don't copy the password into buffer by pressing Ctrl+C https://bugs.launchpad.net/bugs/477891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477891] Re: keepassx don't copy the password into buffer by pressing Ctrl+C
I observed this problem (same as comment #3), but after a reboot it went away and stayed away for a while (weeks). I figured the explanation of comment #4 was probably why. I just noticed it has occurred. I re-enabled the PPA that had been disabled on my 9.04 to 9.10 upgrade, and upgraded to 0.4.3, but the problem is still there. It might get resolved by a reboot again, but if this is reoccurring, there's clearly something broken. Reinhard Tartler wrote: seems like an upstream issue to me I don't see any reports upstream. Seems more likely that there is a specific interaction with Ubuntu. If an OS reboot temporarily fixes the problem, but an application restart does not, chances are there is something in the Ubuntu/GNOME environment that is ceasing to work after a period of time. I see an old Debian bug that appears to describe the same symptoms and offers a patch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414171 I'm guessing this occurrence has a slightly different cause, otherwise it wouldn't work some of the time. I don't see any upstream bugs so I created one: https://sourceforge.net/tracker/?func=detailaid=3024974group_id=166631atid=839779 ** Bug watch added: Debian Bug tracker #414171 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414171 ** Bug watch added: SourceForge.net Tracker #3024974 http://sourceforge.net/support/tracker.php?aid=3024974 -- keepassx don't copy the password into buffer by pressing Ctrl+C https://bugs.launchpad.net/bugs/477891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477891] Re: keepassx don't copy the password into buffer by pressing Ctrl+C
I wrote: It might get resolved by a reboot again... Confirmed. After a reboot, the clipboard functionality of keepassx was restored. So what is changing during a session to break it? -- keepassx don't copy the password into buffer by pressing Ctrl+C https://bugs.launchpad.net/bugs/477891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509544] Re: wishlist: add indication of background tab buffer change
...I think I'd like it to change to bold text. That probably would have been my first pick too. It fits the model used by other applications. Though if tabs adjust their width to the text, that can trigger undesired movement in the tab bar contents. (It looks like ROXTerm tabs are fixed width, and if so, this concern isn't applicable.) ...the close button icon will change. That sounds OK too, though there isn't a good UI metaphor or precedent for using the close button real estate as a notification area. (I've always found close buttons on tabs that aren't in the foreground to be problematic. Occasionally it is handy to be able to close a tab without bringing it into the foreground. But sometimes it can make it too easy to close the wrong tab. I think my ideal tab close button would stay hidden unless the tab was in the foreground and the mouse was hovering over the tab corner. This requires some user training to know that it is there, but affords more space for titles.) ...new option...Show terminal status in close buttons. The background only flashes for beeps... Off the top of my head, I can't think of any good use cases that I personally encounter where a general change notification would be useful. Sure, there's the rare occasion when I'm moving or copying a large file, and an indication of when that completes could be handy. Aside from that, I think it would mostly get triggered by the error messages spit out by ssh when a network connection drops and it reconnects. Due to automation and 'screen' such a disconnect has no real impact, so it isn't something I'd want my attention drawn to. I'd have to try it for a while to see whether it ends up being more useful or more distraction, so I'd want to make sure that the status notification can be disabled independent of the beep notification, which I do find useful. I'll provide some more feedback after I've used the svn version for a while and give an opinion on whether this feature should be on or off by default. -- wishlist: add indication of background tab buffer change https://bugs.launchpad.net/bugs/509544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376879] Re: grub2 installer modifies grub 0.97 menu.lst incorrectly and fails to chainload grub2
Colin Watson wrote: grub2 was released in jaunty for testing only... The instructions for upgrading to Ubuntu 9.10 warns that there are problems with some systems when identifying the root partition via UUID. The instructions imply that although this impacts both grub legacy and grub2, the workaround appears far cleaner in grub2. Therefore it is a logical preparation step for a 9.10 upgrade to start by first upgrading to grub2, then applying the setting not to use UUID, and confirming that all works before doing the dist upgrade. Given this, I was surprised when I found this known bug to still be present in 9.04. Fortunately I had already read about the workaround in these grub2 upgrade guides: http://www.howtoforge.com/how-to-install-grub-2-on-ubuntu-9.04 http://www.ubuntu-inside.me/2009/06/howto-upgrade-to-grub2-on-ubuntu-jaunty.html So I'll add another vote for getting this resolved on 9.04. -- grub2 installer modifies grub 0.97 menu.lst incorrectly and fails to chainload grub2 https://bugs.launchpad.net/bugs/376879 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512201] [NEW] no keys available dialog doesn't give sufficient diections
Public bug reported: Binary package hint: cryptkeeper In Ubuntu 9.04 with Cryptkeeper 0.9.3... If no appropriate key type is available when you go to encrypt something, a helpful dialog appears informing the user that they should create a key using the Passwords and Encryption keys application, then launches that application. However the message falls just a bit short of being as helpful as it could be, as it fails to tell the user what type of key they need to create. (Apparently it is a PGP key.) ** Affects: cryptkeeper (Ubuntu) Importance: Undecided Status: New -- no keys available dialog doesn't give sufficient diections https://bugs.launchpad.net/bugs/512201 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485528] [NEW] loadkeys reports killkey called with bad index
Public bug reported:
Binary package hint: kbd
On Ubuntu 9.04 using kbd 1.14.1-4ubuntu4 I used showkey (with no
options) to find the keycode for a couple of keys on my Acer Aspire
8930G notebook that had been reporting no evens in X (xev). showkey
reported 435 and 434 as the keycodes. I created a keymap like:
keymaps 0-63
# map Euro key to Home
keycode 435 = Home
# map $ key to End
keycode 434 = End
and processed it with loadkeys from the console, which reported:
killkey called with bad index 435
A quick search turned up the source for a version of loadkeys.c that
shows:
http://dev.laptop.org/~mstone/sources/expanded_srpms/kbd-1.12-22.fc7/kbd-1.12/src/loadkeys.y
#define NR_KEYS 256
[...]
static void
killkey(int index, int table) {
/* roughly: addkey(index, table, K_HOLE); */
if (index 0 || index = NR_KEYS)
lkfatal0(_(killkey called with bad index %d), index);
[...]
From what I can tell, 435 is in fact a keycode (and not one of the other
things showkey can report), and is supposed to be a decimal number, so that
leads me to wonder if NR_KEYS needed to be updated to reflect the current
capabilities of the keyboad driver.
I'll try grabbing the proper source, increasing that limit (512?), and
giving it a spin to see if it chokes elsewhere.
** Affects: kbd (Ubuntu)
Importance: Undecided
Status: New
--
loadkeys reports killkey called with bad index
https://bugs.launchpad.net/bugs/485528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214470] Re: gdm screen uses virtual screen size instead of actual
*** This bug is a duplicate of bug 223613 *** https://bugs.launchpad.net/bugs/223613 Duplicate of bug #223613 This is incorrect. That was a usplash problem, not GDM. -- gdm screen uses virtual screen size instead of actual https://bugs.launchpad.net/bugs/214470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214470] Re: gdm screen uses virtual screen size instead of actual
*** This bug is a duplicate of bug 223613 *** https://bugs.launchpad.net/bugs/223613 Matthew Koyle wrote: My GDM resolution should have been 1280x1024 but my greeters did not appear properly. Rather, it looked as though the greeter was stretched to 1600x1200 and I could not see the bottom and right sides of the greeter. Likewise. In my xorg.conf I had a line in the screen section: virtual 1600 1200 Changing that line to 1280 1024 fixed the GDM greeter resolution problem for me. Seems to have had no effect - at least with an X restart. -- gdm screen uses virtual screen size instead of actual https://bugs.launchpad.net/bugs/214470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251456] Re: Nautilus drag and drop crash
I've been seeing this frequently in 9.04. (Didn't notice it in 8.10 on the same machine.) I can reproduce it easily. Sometimes the crash occurs as soon as the drag operation is commenced. Lately I've been noticing it when copying files from an SMB mount. I haven't tested whether the problem is exclusive to that. I have been seeing stuff like: [415439.660824] CIFS VFS: No response for cmd 50 mid 30 [415439.811663] CIFS VFS: No response for cmd 114 mid 33 in the kernel log, but I've seen those at times other than when nautilus crashes. (They seem to be another artifact of the buggy 9.04 environment. Don't recall seeing them in 8.10.) My /var/crash directory is empty. But I can easily follow any recommended procedure for capturing crash data. (This leaves the desktop devoid of icons. Is there a recommended procedure for restarting the nautilus instance used to render the desktop?) -- Nautilus drag and drop crash https://bugs.launchpad.net/bugs/251456 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251456] Re: Nautilus drag and drop crash
There are two other bugs that report the same symptom: Bug #197224 in language-pack-gnome-eu (Ubuntu): “nautilus crashed with SIGSEGV in g_file_query_info()” Bug #224943 in nautilus (Ubuntu): “Nautilus crashes when dragdropping files to localized folders” But both had an underlying cause relating to translations. I wouldn't expect that to be applicable to an English installation. -- Nautilus drag and drop crash https://bugs.launchpad.net/bugs/251456 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382640] Re: xorg crashes (nvidia 180.51)
After updating to 185.18.14 I still experienced a crash. kernel log: NVRM: Xid (0001:00): 8, Channel 0001 NVRM: Xid (0001:00): 13, 0003 8297 1b0c 1000f010 0040 NVRM: Xid (0001:00): 13, 0003 8297 1310 0040 NVRM: Xid (0001:00): 13, 0003 8297 0f04 0040 NVRM: Xid (0001:00): 13, 0003 8297 0f04 0040 NVRM: Xid (0001:00): 13, 0003 8297 0f04 0040 NVRM: Xid (0001:00): 13, 0003 8297 0f04 0040 NVRM: Xid (0001:00): 13, 0003 8297 0f04 0040 CE: hpet increasing min_delta_ns to 170856 nsec CE: hpet increasing min_delta_ns to 256284 nsec And: # fgrep gdm_slave_xioerror_handler daemon.log Jun 29 01:49:30 fringe gdm[3226]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Worked fine before upgrading to Jaunty. -- xorg crashes (nvidia 180.51) https://bugs.launchpad.net/bugs/382640 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381969] Re: window refresh/redraw/repaint problems with QT4 apps.
After updating to 185.18.14 there is no notable changes to the previously reported symptoms. The repaint problems in the help viewer for Bookmarkbridge are as bad if not slightly worse compared to the earlier test. And Keepassx is currently not exhibiting any symptoms, as before. However, I'm now seeing a new problem since this driver update. I had MythTV front-end playing back a video in a window while restoring a Firefox session. At some point during the session restore, the color in the video shifted (faces turned blue, for example). Exiting and restarting MythTV front-end or switching to a different video did not reset the color palette, however switching to a different virtual desktop and back did. -- window refresh/redraw/repaint problems with QT4 apps. https://bugs.launchpad.net/bugs/381969 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381969] Re: window refresh/redraw/repaint problems with QT4 apps.
I've posted a new version of the -nvidia driver to our xorg-edgers PPA, would you mind testing it either on Jaunty... I'll give it a spin, though a recent update (within the last two weeks I'd guess) has vastly improved the situation. As far as I can see from my logs, I'm still using the same version of libqtcore4 (4.5.0-0ubuntu4.1), as when I reported the bug, so that must not have been the culprit. And nvidia-glx-180 is still 180.44-0ubuntu1. Of course I've had kernel and other upgrades. I originally wrote: Specific apps. where I've seen problems: The help viewer for Bookmarkbridge. The entry edit dialog in Keepassx. Last time I tested the help viewer for Bookmarkbridge, it appeared to work normally. Originally the repaint problem was so bad that it was unusable. ...actually, retesting it, it still does exhibit symptoms in the form of delayed repaints, but much better than it was. KeepassX is also improved. Last I tested it I still observed some repaint problems with the dialog buttons. Today, I can't observer any problems. Now with the symptoms baselined, I'll try the updated nvidia driver and retest. -- window refresh/redraw/repaint problems with QT4 apps. https://bugs.launchpad.net/bugs/381969 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391854] Re: Preferred Applications should update /etc/alternatives
See related bug #185247. -- Preferred Applications should update /etc/alternatives https://bugs.launchpad.net/bugs/391854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391854] [NEW] Preferred Applications should update /etc/alternatives
Public bug reported: Binary package hint: gnome-control-center Binary package hint: gnome-control-center Using Ubuntu Jaunty, specifying a referred web browser via the GNOME Preferred Applications control applet doesn't update the /etc/alternatives/x-www-browser symlink. As a result certain operations within the GUI result in the incorrect browser being used. If Preferred Applications is the visible and and most accessible mechanism for setting browser references on Ubuntu desktops, then it would be logical to integrate it with the Debian /etc/alternatives mechanism. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Preferred Applications should update /etc/alternatives https://bugs.launchpad.net/bugs/391854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 355155] Re: Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
Manoj Iyer wrote: Can someone please try the kernel in http://people.ubuntu.com/~manjo/lp355155-jaunty/ and report if that fixes the problem ? Can you specify what has changed in this kernel and what your theory is as to the cause of these symptoms? I've been holding off on trying new kernels to resolve this, because currently the Alsa upgrade script[1] doesn't seem to support kernels newer[2] than 2.6.28-11, and installing Alsa from source seems to be necessary in order to get working sound (as was the case with 8.10 too) with my hardware. Fortunately the symptoms I'm experiencing are comparatively mild, and not greatly interfering with my ability to use the machine. (I'm experiencing about one crash a week in a manner fitting the description of this ticket, problems surrounding high network activity, and high CPU usage by X.) 1. http://ubuntuforums.org/showthread.php?t=1046137 2. http://ubuntuforums.org/showpost.php?p=7429366postcount=304 -- Clocksource tsc unstable leads to lockups in Ubuntu Jaunty https://bugs.launchpad.net/bugs/355155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 355155] Re: Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
laysan_a wrote: Now my system is...very sluggish...xorg is using a lot of processor time (10 - 20% with only a couple of windows open). I've been experiencing this as well for about a week or so. It's hard to say whether this is a symptom of this bug - which is rapidly turning into a kitchen sink catch-all for problems that cause crashes - or something independent. I haven't gone looking for a more specific ticket against X, but if anyone runs across one, post a reference to it here. The best bet for getting these crashes resolved is to group together reports that all share very specific symptoms, like the originally reported Clocksource tsc unstable log entries, and let the developers work their way through eliminating each specific symptom. -- Clocksource tsc unstable leads to lockups in Ubuntu Jaunty https://bugs.launchpad.net/bugs/355155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387657] [NEW] aa-logprof: doesn't handle large logs
Public bug reported: Binary package hint: apparmor Ubuntu 8.04.2 Package: apparmor-utils Version: 2.1+1075-0ubuntu9.2 My first experience with AppArmor was finding a kernel log file that was full of 800 MB of AppArmor warnings from Samba and CUPS. I'm not sure what suddenly enabled AppArmor on this LTS system, but while fixing the problem I noticed aa-logprof, while processing an 800 MB log file, drove the load average up into the high 40's. I suspect it was trying to load the whole thing into memory (on a system with 1 GB of RAM). I'd recommend revising the architecture so that it processes the lines as it sees them. I worked around the problem by splitting the file into a dozen 75MB chunks. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- aa-logprof: doesn't handle large logs https://bugs.launchpad.net/bugs/387657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387660] [NEW] aa-logprof: mangled usr.sbin.cupsd profie
Public bug reported: Binary package hint: apparmor Ubuntu 8.04.2 Package: apparmor-utils Version: 2.1+1075-0ubuntu9.2 When using aa-logprof to update the usr.sbin.cupsd profie, I noticed a diff after the update showed the file was mangled in several ways: 1. The file contained two profiles, and the second (/usr/lib/cups/backend/cups-pdf) was missing. 2. Comments were stripped out. 3. The ordering of the lines was altered, resulting in a far noisier diff than necessary. Obviously #1 is the serious problem, potentially resulting in breakage. #2 results in information loss. And #3 makes maintenance more of a chore. Hopefully this has been resolved in newer versions... ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- aa-logprof: mangled usr.sbin.cupsd profie https://bugs.launchpad.net/bugs/387660 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387663] [NEW] aa-logprof: doesn't remove redundant rules
Public bug reported: Binary package hint: apparmor Ubuntu 8.04.2 Package: apparmor-utils Version: 2.1+1075-0ubuntu9.2 My understanding of the aa-logprof documentation is that it is supposed to remove specific rules that are obviated by broader rules, but examining the diff after a profile update seems to show otherwise: # rcsdiff usr.sbin.smbd .RCS/usr.sbin.smbd,v [...] 19a19,21 /data/ r, /data/** krw, [...] 30a34,36 /var/log/samba/clients/* a, /var/log/samba/cores/smbd/ rw, /var/log/samba/cores/smbd/** rw, 34,36c40,44 [...] /video/ r, /video/** krw, /video2/**/ r, /video2/mythtv/1024_2009013120.mpg r, /video2/mythtv/1029_20090310173000.mpg r, Many of those rules appear redundant, and I'm sure at least a few are, such as the last 3 lines. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- aa-logprof: doesn't remove redundant rules https://bugs.launchpad.net/bugs/387663 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387669] [NEW] aa-logprof: doesn't ignore RCS directory
Public bug reported: Binary package hint: apparmor Ubuntu 8.04.2 Package: apparmor-utils Version: 2.1+1075-0ubuntu9.2 A not uncommon practice is to use RCS to track changes to system configuration files. With most *.d/ directories on Debian systems you can create an RCS subdirectory, and it will be safely ignored. If you create /etc/apparmor.d/RCS, aa-logprof will attempt to parse the files in that directory and produce errors. I'm not sure if this directory processing behavior occurs just in the helper tools, like aa- logprof, or if the main AppArmor program does this as well. Either way, it should behave more consistently with other Debian tools. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- aa-logprof: doesn't ignore RCS directory https://bugs.launchpad.net/bugs/387669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387663] Re: aa-logprof: doesn't remove redundant rules
/dir/ and /dir have different meanings... Thanks. I figured that might be the case. Same true for /dir/ vs. /dir/** I presume. But what about: /video2/**/ r, /video2/mythtv/1024_2009013120.mpg r, /video2/mythtv/1029_20090310173000.mpg r, These seem redundant, unless that first rule should be /video2/** without the trailing slash. -- aa-logprof: doesn't remove redundant rules https://bugs.launchpad.net/bugs/387663 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 355155] Re: Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
Chem. Imbalance wrote: In the meantime, I've regressed back to XP just so I can have a stable machine. If your machine ran stable with 8.10, wouldn't that be the logical OS and version to regress to if you're having problems with 9.04? -- Clocksource tsc unstable leads to lockups in Ubuntu Jaunty https://bugs.launchpad.net/bugs/355155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355155] Re: Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
Pit. wrote on 2009-04-04: It appear after update from 2.6.28-6 on 2.6.28-8 kernel and upper. Has anyone tried reverting to an older kernel? It's been established that video hardware is not the common link for these symptoms, but a hardware commonality seems likely. If it was just a general problem with the kernel, thousands of users would be affected instead of hundreds. Lets see if we can spot a commonality. Please run following commands: ( uname -r ; echo ; lspci -k ; echo ; lsmod ) /tmp/drivers.txt and post drivers.txt as an attachment. (If the data is collected consistently, a bit of Perl scripting should be able to produce a report of any commonalities.) I see I have this: Ethernet controller: Attansic Technology Corp. L1e Gigabit Ethernet Adapter (rev b0) in common with the original poster, but I'm not actively using the wired Ethernet on the affected machine. My suspicion was more towards the Intel wireless controller driver, as wireless has become flaky since upgrading to 9.04, but the OP has an Atheros wireless controller. ** Attachment added: drivers.txt http://launchpadlibrarian.net/27708656/drivers.txt -- Clocksource tsc unstable leads to lockups in Ubuntu Jaunty https://bugs.launchpad.net/bugs/355155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382640] Re: xorg crashes (nvidia 180.51)
I saw the same symptoms with 180.44-0ubuntu1 on 9.04: daemon.log:Jun 1 15:39:18 fringe gdm[3199]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 But nothing unusual in Xorg.0.log*. Perhaps resolved in the 180.60 version, which someone commented in Bug #355155 resolved a crash problem. -- xorg crashes (nvidia 180.51) https://bugs.launchpad.net/bugs/382640 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338669] apport-collect data
Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: qt4-x11 ProcEnviron: PATH=(custom, user) SHELL=/bin/tcsh LANG=en_US.UTF-8 Uname: Linux 2.6.28-12-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare users -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381969] [NEW] window refresh/redraw/repaint problems with QT4 apps.
Public bug reported: Binary package hint: libqtcore4 I'm seeing symptoms similar to what is described in Bug #338669 except I'm using GNOME instead of KDE and have an Nvidia video card (nvidia- glx-180 180.44-0ubuntu1). The symptom seems to be restricted to QT4 apps, with libqtcore4 as a common component. Specific apps. where I've seen problems: The help viewer for Bookmarkbridge. The entry edit dialog in Keepassx. The distortions I've observed aren't as extensive as those described in Bug #295079, but this is potentially a duplicate of that bug's circumstances (GNOME/Nvidia). ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New -- window refresh/redraw/repaint problems with QT4 apps. https://bugs.launchpad.net/bugs/381969 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381969] apport-collect data
Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: qt4-x11 ProcEnviron: PATH=(custom, user) SHELL=/bin/tcsh LANG=en_US.UTF-8 Uname: Linux 2.6.28-12-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare users -- window refresh/redraw/repaint problems with QT4 apps. https://bugs.launchpad.net/bugs/381969 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
Sorry, apport-collect data sent to wrong ticket. I just filed Bug #381969 which covers symptoms similar to what is described in this bug, except I'm using GNOME instead of KDE and have an Nvidia video card (nvidia-glx-180 180.44-0ubuntu1). -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255226] Re: sysklogd doesn't use logrotate
For a long time I've used a workaround for this problem that moves all
sysklogd generated files to /var/log/syslog/ and then uses this
logrotate config file:
/var/log/syslog/*.log {
olddir /var/log/syslog/old
sharedscripts
postrotate
/etc/init.d/sysklogd reload-or-restart /dev/null
endscript
}
Solves the problem cleanly, and I wish Debian would adopt this, but
they're understandably concerned about moving the location of common log
files.
Another approach would be to patch sysklogd to have a command line
option where it will output the definitive list of log files parsed from
its config file (supplanting the external shell script hack).
Unfortunately you can't simply do `sysklogd --listfiles` in logrotate,
due to its inflexibility. (Boggles the mind why a log rotation program
was written in C instead of Perl. See also http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=326421 and http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=353663 )
** Bug watch added: Debian Bug tracker #326421
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326421
** Bug watch added: Debian Bug tracker #353663
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353663
--
sysklogd doesn't use logrotate
https://bugs.launchpad.net/bugs/255226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357518] Re: udhcpc doesn't set hostname in discover packet
MatthiasH wrote: ...I learned that this is a configuration issue: Adding the option hostname $(hostname) to the configuration... Right, it seems I noted that in my original report: Modifying /etc/network/interfaces to include a hostname argument appeared to resolve the problem. I believe the bug I was pointing out is that the behavior is inconsistent with the other two DHCP client packages. ** Summary changed: - udhcpc doesn't set hostname in doscover packet + udhcpc doesn't set hostname in discover packet -- udhcpc doesn't set hostname in discover packet https://bugs.launchpad.net/bugs/357518 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365932] [NEW] directing logs to a broadcast address results in sendto: Permission denied
Public bug reported: Binary package hint: sysklogd If you modify your /etc/syslog.conf to have a line like: *.crit @192.168.0.255 restart sysklogd, and then run: logger -p local0.crit -t foo message you'll observe in /var/log/daemon.log: Apr 24 04:14:29 host syslogd 1.5.0#1ubuntu1: restart. Apr 24 04:15:13 host syslogd: sendto: Permission denied It appears this is because syslog isn't enabling broadcast on the socket it is using. See: http://www.experts-exchange.com/Programming/System/Linux/Q_20862022.html Observed in Ubuntu 8.04 and Debian Etch (I haven't tested 8.10; will you guys open an upstream ticket or shall I? I haven't checked to see if one already exists in the DBTS). Being able to send logs to a broadcast address is supposedly something that is supposed to work, according to various third party documents on configuring syslog (not syslog-ng). ** Affects: sysklogd (Ubuntu) Importance: Undecided Status: New -- directing logs to a broadcast address results in sendto: Permission denied https://bugs.launchpad.net/bugs/365932 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Bryan McLellan wrote: Tom Metro wrote: I'll have to take a look at ubuntu-minimal to see what it is. It's a meta package... I figured that from the name, but I wondered what packages it pulled in, and what the consequences were for removing it were. Uninstalling it would mean that in the future if another package was added to to the meta package, you wouldn't get that additional package on upgrade. Which sounds fairly low risk, but something one would ideally want to avoid. You could also remove the dhcp3-client package with --force-depends, which just runs the risk that it gets reinstalled later during an upgrade. There's probably a complex pinning solution too, but I can't fathom it. I couldn't figure out a way around it. Any combination I came up with (like putting dhcp3-client on hold, then removing it), just left the package system in a broken state. More importantly, on Hardy there are additional dependencies on dhcp3-client. dhcdbd depends on it, which provides the DBus interface to dhcp3-client that's used by network manager, which in turn Network Manager depends on, which in turn ubuntu-desktop depends on. The resolutions offered up by aptitude (supposedly the best tool for resolving dependency issues) all involved uninstalling more packages than I cared to. To work around this I ended up creating a dummy package using the equivs package. That lets me replace the real dhcp3-client with a dummy one, which uninstalled the dhcp3-client binaries and scripts. All this makes me wonder if ubuntu-minimal ought to be dependent on the generic dhcp-client (which dhcp3-client, dhcpcd, and udhcpc all provide), rather than a specific package. (Of course on Hardy that won't fix the dhcdbd dependency. I'm guessing that means dhcp3 is probably the only client Network Manager knows how to control.) I'm also wondering if uninstalling dhcp3-client was even necessary. I noticed when I installed udhcpc that it didn't cause any conflicts, even though it ought to have conflicted with another package providing dhcp-client. Either udhcpc isn't correctly tagged as providing dhcp-client, or the two can peacefully coexist. Looks like dhcpcd has dhcp-client listed as a conflict, while udhcpc doesn't. Given that they all are driven by the sane interfaces config file, I'd expect there to be conflicts. I'd like to understand better how that works. Is each overwriting the other's ifupdown scripts? Is there a common script with a bunch of -x tests to see which binaries are present? I did test and confirm that dhcpcd=1:3.2.3-1.1 does work on alias interfaces on intrepid. Unfortunately this doesn't work on Hardy with dhcpcd=1:3.0.17-2: # init.d/networking restart * Reconfiguring network interfaces... Error, eth0: dhcpcd not running dhcpcd.sh: interface eth0 has been configured with new IP=192.168.0.203 * Stopping NTP server ntpd ...done. * Starting NTP server ntpd ...done. Error, eth0:1: ioctl SIOCSIFFLAGS: Cannot assign requested address Failed to bring up eth0:1. [...] ...done. Looks like the usual failure, though in a bit different format than what ifconfig produces, suggesting it is making its own syscalls, and they're failing in the kernel code. At least it positively states that it failed to bring up the interface (confirmed), unlike dhcp3-client. A second look at the interfaces man page shows that the DHCP configuration directives there are supported by udhcpc in addition to dhcpcd. I hadn't noticed that before, and the udhcpc documentation omits to mention it (should probably file a bug for that). Given that udhcpc spits out warnings, but did appear to work when invoked directly on Hardy, I'm going to try that next. Hurray, it finally worked: # init.d/networking restart * Reconfiguring network interfaces... RTNETLINK answers: No such process udhcpc (v0.9.9-pre) started Sending discover... Sending select for 192.168.0.203... Lease of 192.168.0.203 obtained, lease time -1 Resetting default routes adding dns 192.168.0.35 * Stopping NTP server ntpd ...done. * Starting NTP server ntpd ...done. udhcpc (v0.9.9-pre) started SIOCSIFFLAGS: Cannot assign requested address Sending discover... Sending select for 192.168.0.238... Lease of 192.168.0.238 obtained, lease time -1 Resetting default routes adding dns 192.168.0.35 * Stopping NTP server ntpd ...done. Ignoring unknown interface eth1=eth1. Ignoring unknown interface eth2=eth2. Ignoring unknown interface ath0=ath0. Ignoring unknown interface wlan0=wlan0. [ OK ] * Starting NTP server ntpd ...done. # ifconfig eth0 Link encap:Ethernet HWaddr 00:04:...:d1:33 inet addr:192.168.0.203 Bcast:192.168.0.255 Mask:255.255.255.0 [...] eth0:1Link encap:Ethernet HWaddr 00:04:...:d1:33 inet addr:192.168.0.238 Bcast:192.168.0.255 Mask:255.255.255.0 I did have to apply some additional tweaks to interfaces to get udhcpc to behave
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Here's the summary how how to work around this bug: First, if you're using Dnsmasq on the server-side you might run into Bug #327703. The Dnsmasq author has a patched version available. 1. On Hardy, download and install the attached dhcp3-client dummy package: % sudo dpkg -i dhcp3-client-dummy_3.0.6.dfsg-1ubuntu9_all.deb and then put it on hold: % sudo aptitude hold dhcp3-client On Intrepid, remove the dhcp3-client package and permit ubuntu-minimal to also get removed (or build your own dummy package using the equivs package). 2. Install udhcpc: % sudo aptitude install udhcpc 3. Add your virtual interface to /etc/network/interfaces, while also adding unique hostname and client arguments for both. The client identifiers can match the corresponding host names or be any other reasonable string, as long as they are not used by any other DHCP clients on your network. auto eth0 iface eth0 inet dhcp hostname primary-host client primary-client-id auto eth0:1 iface eth0:1 inet dhcp hostname virtual-host client virtual-client-id 4. Restart the network subsystem: % sudo /etc/init.d/networking restart ** Attachment added: Dummy package to permit removing the real dhcp3-client package http://launchpadlibrarian.net/25005944/dhcp3-client-dummy_3.0.6.dfsg-1ubuntu9_i386.deb -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Bryan McLellan wrote: Tom Metro wrote: I'll have to take a look at ubuntu-minimal to see what it is. It's a meta package... I figured that from the name, but I wondered what packages it pulled in, and what the consequences were for removing it were. Uninstalling it would mean that in the future if another package was added to to the meta package, you wouldn't get that additional package on upgrade. Which sounds fairly low risk, but something one would ideally want to avoid. You could also remove the dhcp3-client package with --force-depends, which just runs the risk that it gets reinstalled later during an upgrade. There's probably a complex pinning solution too, but I can't fathom it. I couldn't figure out a way around it. Any combination I came up with (like putting dhcp3-client on hold, then removing it), just left the package system in a broken state. More importantly, on Hardy there are additional dependencies on dhcp3-client. dhcdbd depends on it, which provides the DBus interface to dhcp3-client that's used by network manager, which in turn Network Manager depends on, which in turn ubuntu-desktop depends on. The resolutions offered up by aptitude (supposedly the best tool for resolving dependency issues) all involved uninstalling more packages than I cared to. To work around this I ended up creating a dummy package using the equivs package. That lets me replace the real dhcp3-client with a dummy one, which uninstalled the dhcp3-client binaries and scripts. All this makes me wonder if ubuntu-minimal ought to be dependent on the generic dhcp-client (which dhcp3-client, dhcpcd, and udhcpc all provide), rather than a specific package. (Of course on Hardy that won't fix the dhcdbd dependency. I'm guessing that means dhcp3 is probably the only client Network Manager knows how to control.) I'm also wondering if uninstalling dhcp3-client was even necessary. I noticed when I installed udhcpc that it didn't cause any conflicts, even though it ought to have conflicted with another package providing dhcp-client. Either udhcpc isn't correctly tagged as providing dhcp-client, or the two can peacefully coexist. Looks like dhcpcd has dhcp-client listed as a conflict, while udhcpc doesn't. Given that they all are driven by the sane interfaces config file, I'd expect there to be conflicts. I'd like to understand better how that works. Is each overwriting the other's ifupdown scripts? Is there a common script with a bunch of -x tests to see which binaries are present? I did test and confirm that dhcpcd=1:3.2.3-1.1 does work on alias interfaces on intrepid. Unfortunately this doesn't work on Hardy with dhcpcd=1:3.0.17-2: # init.d/networking restart * Reconfiguring network interfaces... Error, eth0: dhcpcd not running dhcpcd.sh: interface eth0 has been configured with new IP=192.168.0.203 * Stopping NTP server ntpd ...done. * Starting NTP server ntpd ...done. Error, eth0:1: ioctl SIOCSIFFLAGS: Cannot assign requested address Failed to bring up eth0:1. [...] ...done. Looks like the usual failure, though in a bit different format than what ifconfig produces, suggesting it is making its own syscalls, and they're failing in the kernel code. At least it positively states that it failed to bring up the interface (confirmed), unlike dhcp3-client. A second look at the interfaces man page shows that the DHCP configuration directives there are supported by udhcpc in addition to dhcpcd. I hadn't noticed that before, and the udhcpc documentation omits to mention it (should probably file a bug for that). Given that udhcpc spits out warnings, but did appear to work when invoked directly on Hardy, I'm going to try that next. Hurray, it finally worked: # init.d/networking restart * Reconfiguring network interfaces... RTNETLINK answers: No such process udhcpc (v0.9.9-pre) started Sending discover... Sending select for 192.168.0.203... Lease of 192.168.0.203 obtained, lease time -1 Resetting default routes adding dns 192.168.0.35 * Stopping NTP server ntpd ...done. * Starting NTP server ntpd ...done. udhcpc (v0.9.9-pre) started SIOCSIFFLAGS: Cannot assign requested address Sending discover... Sending select for 192.168.0.238... Lease of 192.168.0.238 obtained, lease time -1 Resetting default routes adding dns 192.168.0.35 * Stopping NTP server ntpd ...done. Ignoring unknown interface eth1=eth1. Ignoring unknown interface eth2=eth2. Ignoring unknown interface ath0=ath0. Ignoring unknown interface wlan0=wlan0. [ OK ] * Starting NTP server ntpd ...done. # ifconfig eth0 Link encap:Ethernet HWaddr 00:04:...:d1:33 inet addr:192.168.0.203 Bcast:192.168.0.255 Mask:255.255.255.0 [...] eth0:1Link encap:Ethernet HWaddr 00:04:...:d1:33 inet addr:192.168.0.238 Bcast:192.168.0.255 Mask:255.255.255.0 I did have to apply some additional tweaks to interfaces to get udhcpc to behave
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Here's the summary how how to work around this bug: First, if you're using Dnsmasq on the server-side you might run into Bug #327703. The Dnsmasq author has a patched version available. 1. On Hardy, download and install the attached dhcp3-client dummy package: % sudo dpkg -i dhcp3-client-dummy_3.0.6.dfsg-1ubuntu9_all.deb and then put it on hold: % sudo aptitude hold dhcp3-client On Intrepid, remove the dhcp3-client package and permit ubuntu-minimal to also get removed (or build your own dummy package using the equivs package). 2. Install udhcpc: % sudo aptitude install udhcpc 3. Add your virtual interface to /etc/network/interfaces, while also adding unique hostname and client arguments for both. The client identifiers can match the corresponding host names or be any other reasonable string, as long as they are not used by any other DHCP clients on your network. auto eth0 iface eth0 inet dhcp hostname primary-host client primary-client-id auto eth0:1 iface eth0:1 inet dhcp hostname virtual-host client virtual-client-id 4. Restart the network subsystem: % sudo /etc/init.d/networking restart ** Attachment added: Dummy package to permit removing the real dhcp3-client package http://launchpadlibrarian.net/25005944/dhcp3-client-dummy_3.0.6.dfsg-1ubuntu9_i386.deb -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357518] [NEW] udhcpc doesn't set hostname in doscover packet
Public bug reported: When invoking udhcpc (0.9.8cvs20050303-2 on Ubuntu 8.04) via /etc/network/interfaces, it appears as if it does not send the host name in the discover packet, as occurs with dhcp3-client and dhcpcd. I haven't confirmed this with a packet sniffer, but my DHCP server behaved as if this was the case (it assigned a dynamic IP address rather than matching a rule to assign a static address based on the supplied host name). Modifying /etc/network/interfaces to include a hostname argument appeared to resolve the problem. (I ran across this while developing a work around for Bug #351378.) ** Affects: udhcp (Ubuntu) Importance: Undecided Status: New -- udhcpc doesn't set hostname in doscover packet https://bugs.launchpad.net/bugs/357518 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357522] [NEW] udhcpc man page should reference /etc/network/interfaces
Public bug reported: While using udhcpc as a replacement for dhcp3-client to work around a bug (Bug #351378), I was heading down the path of creating a custom up script to invoke udhcpc directly when I happened to notice in the DHCP section of the interfaces man page that it supported udhcpc. The connection between udhcpc and /etc/network/interfaces should be made more explicit by adding a reference to it in the udhcpc man page. (And this should be pushed upstream to Debian.) ** Affects: udhcp (Ubuntu) Importance: Undecided Status: New -- udhcpc man page should reference /etc/network/interfaces https://bugs.launchpad.net/bugs/357522 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
I've opened Bug #356800, ifconfig fails to initiaize a virtual interface with a zero IP address. This bug should be made dependent on it. (I didn't see a way to do that.) -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 356800] [NEW] ifconfig fails to initiaize a virtual interface with a zero IP address
Public bug reported: Binary package hint: net-tools ifconfig in net-tools 1.60-19ubuntu1 (Ubuntu 8.04) and 1.60-19ubuntu3 (Ubuntu 8.10) fails to initialize a virtual interface to a zero (0 or 0.0.0.0) IP address: % sudo /sbin/ifconfig eth0:1 inet 0 up SIOCSIFFLAGS: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address This behavior apparently used to work and is depended upon by several DHCP packages, including the default dhcp3, and udhcp, as the way they instantiate or reset the virtual interface to a deconfigured state prior to obtaining a configuration via DHCP. See Bug #351378 for the full context of the problem and a strace of the failure. ** Affects: net-tools (Ubuntu) Importance: Undecided Status: New -- ifconfig fails to initiaize a virtual interface with a zero IP address https://bugs.launchpad.net/bugs/356800 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
I've opened Bug #356800, ifconfig fails to initiaize a virtual interface with a zero IP address. This bug should be made dependent on it. (I didn't see a way to do that.) -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Bryan McLellan wrote: These two errors are because dhclient-script does not support alias interfaces. That may be partly right. I see /sbin/dhclient-script contains the comment: # The alias handling in here probably still sucks. -mdz and there's clearly evidence that it is attempting to support virtual interfaces: if [ -n $alias_ip_address ]; then But real problem seems to be that the script contains lines like: ifconfig $interface inet 0 up and the current version of ifconfig spits out those errors when a virtual interface is set to a zero IP address. The evidence suggests that this worked at one time. In fact, multiple DHCP packages seem to expect this operation to work. I recently tried udhcpc and got familiar results: # udhcpc --hostname=indianpoint --interface=eth0:0 --pidfile=/var/run/udhcpc.eth0:0.pid udhcpc (v0.9.9-pre) started SIOCSIFFLAGS: Cannot assign requested address Sending discover... Sending select for 192.168.0.235... Lease of 192.168.0.235 obtained, lease time -1 Resetting default routes adding dns 192.168.0.35 In this case the error is triggered when udhcpc tries to deconfigure the interface before it configures it, but it happily ignores the error. I'm wondering if one workaround might be to modify the scripts to do: ifconfig $interface down if $interface is virtual. (It seems dhclient-script already contains code to detect virtual interfaces.) I presume there is a reason why deconfiguring an interface is normally performed instead of downing it. (I'm guessing it might make a difference if you were running other networking protocols in addition to IP.) The distinction may be irrelevant for a virtual interface, or just for the vast majority of use cases. Running: ip addr del $IP dev eth0:0 seems to work too, but has the effect of bringing down the virtual interface and you need extra code to obtain the current IP address (passing in a zero does nothing). Before a permanent fix can be determined, it needs to be understood whether this represents a bug in ifconfig, or an intentional change in its behavior. I'm thinking of opening up a ticket against ifconfig that this bug can be dependent on. If you don't use this script, those errors go away. But is that a practical option? Doesn't the script provide a pile of needed glue? Patching the script seems more viable. I can't find any mention in the source of supporting virtual/alias interfaces... The code in dhclient-script is enough to convince me that it was the intention to support virtual interfaces. I'm pretty sure I've read reports that they used to work prior to Ubuntu 8.04. I did test and confirm that dhcpcd=1:3.2.3-1.1 does work on alias interfaces on intrepid. Is it a drop-in replacement that works with the rest of the existing infrastructure in Ubuntu, like /etc/network/interfaces? My next step was going to be using the 'up' argument in an interface stanza for a physical interface to call udhcpc to configure a virtual interface. It looks like this will work, but using something that works with the normal documented way of declaring virtual interfaces in /etc/network/interfaces is preferable. -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Bryan McLellan wrote: Most likely that comment and surely that code is to support the inclusion of an alias definition in your dhclient.conf(5), as opposed to running dhclient on an alias interface. Ah, right. You're probably right. The dhclient.conf(5) man page also mentions pseudo interfaces, which sounds a lot like virtual interfaces: Under some circumstances it can be useful to declare a pseudo-interface and have the DHCP client acquire a configuration for that interface. ... A pseudo-interface is just another state machine running on the interface named real-name, with its own lease and its own state. It also notes: You must also provide a separate client script for the pseudo-interface to do what you want with the IP address. If by that they mean your script will be ran in place of /sbin/dhclient-script, then that would be some more evidence supporting your point that /sbin/dhclient-script doesn't support virtual interfaces, as is. Patching the script seems more viable. The script does provide a lot of glue, but working around it as a debugging technique isolates what errors are coming from the script and what errors are coming from the program itself. I guess I was already pretty convinced that the source of the errors was ifconfig, given that the error can be reproduced external to dhclient and it's scripts by invoking ifconfig directly using the same arguments. The next questions is: is ifconfig broken, or is the manner in which dhclient is calling it broken? I don't believe patching the script will do you any good until the 'Bind socket to interface: No such device' error from dhclient is resolved... My assumption was that this was simply a side effect of the deconfigure step failing, which results in the virtual interface never being created, and thus dhclient has no device to work with. This can be resolved by either 1. patching the code so that it instantiates the virtual interface in a deconfigured state, or 2. special casing virtual interfaces so that the physical interface gets used for the DHCP handshake, while the specified virtual interface is used for the resulting call to ifconfig. (Apparently the latter happens with udhcpc.) Removing dhcp3-client (which removed ubuntu-minimal)... Removing ubuntu-minimal sounds like something to be avoided, but there was mention of people doing that (as a side effect of removing the wireless package) in the bug this one was split off from, and it didn't sound like it caused any problems. I'll have to take a look at ubuntu-minimal to see what it is. ...and installing dhcpcd worked just fine with /etc/network/interfaces ... and thus appears like a clean enough work around. Excellent. Thanks for the suggested workaround. Care to post the /etc/network/interfaces syntax you used for the virtual interface? (In my research I ran across about 3 or 4 variations.) -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Bryan McLellan wrote: These two errors are because dhclient-script does not support alias interfaces. That may be partly right. I see /sbin/dhclient-script contains the comment: # The alias handling in here probably still sucks. -mdz and there's clearly evidence that it is attempting to support virtual interfaces: if [ -n $alias_ip_address ]; then But real problem seems to be that the script contains lines like: ifconfig $interface inet 0 up and the current version of ifconfig spits out those errors when a virtual interface is set to a zero IP address. The evidence suggests that this worked at one time. In fact, multiple DHCP packages seem to expect this operation to work. I recently tried udhcpc and got familiar results: # udhcpc --hostname=indianpoint --interface=eth0:0 --pidfile=/var/run/udhcpc.eth0:0.pid udhcpc (v0.9.9-pre) started SIOCSIFFLAGS: Cannot assign requested address Sending discover... Sending select for 192.168.0.235... Lease of 192.168.0.235 obtained, lease time -1 Resetting default routes adding dns 192.168.0.35 In this case the error is triggered when udhcpc tries to deconfigure the interface before it configures it, but it happily ignores the error. I'm wondering if one workaround might be to modify the scripts to do: ifconfig $interface down if $interface is virtual. (It seems dhclient-script already contains code to detect virtual interfaces.) I presume there is a reason why deconfiguring an interface is normally performed instead of downing it. (I'm guessing it might make a difference if you were running other networking protocols in addition to IP.) The distinction may be irrelevant for a virtual interface, or just for the vast majority of use cases. Running: ip addr del $IP dev eth0:0 seems to work too, but has the effect of bringing down the virtual interface and you need extra code to obtain the current IP address (passing in a zero does nothing). Before a permanent fix can be determined, it needs to be understood whether this represents a bug in ifconfig, or an intentional change in its behavior. I'm thinking of opening up a ticket against ifconfig that this bug can be dependent on. If you don't use this script, those errors go away. But is that a practical option? Doesn't the script provide a pile of needed glue? Patching the script seems more viable. I can't find any mention in the source of supporting virtual/alias interfaces... The code in dhclient-script is enough to convince me that it was the intention to support virtual interfaces. I'm pretty sure I've read reports that they used to work prior to Ubuntu 8.04. I did test and confirm that dhcpcd=1:3.2.3-1.1 does work on alias interfaces on intrepid. Is it a drop-in replacement that works with the rest of the existing infrastructure in Ubuntu, like /etc/network/interfaces? My next step was going to be using the 'up' argument in an interface stanza for a physical interface to call udhcpc to configure a virtual interface. It looks like this will work, but using something that works with the normal documented way of declaring virtual interfaces in /etc/network/interfaces is preferable. -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Bryan McLellan wrote: Most likely that comment and surely that code is to support the inclusion of an alias definition in your dhclient.conf(5), as opposed to running dhclient on an alias interface. Ah, right. You're probably right. The dhclient.conf(5) man page also mentions pseudo interfaces, which sounds a lot like virtual interfaces: Under some circumstances it can be useful to declare a pseudo-interface and have the DHCP client acquire a configuration for that interface. ... A pseudo-interface is just another state machine running on the interface named real-name, with its own lease and its own state. It also notes: You must also provide a separate client script for the pseudo-interface to do what you want with the IP address. If by that they mean your script will be ran in place of /sbin/dhclient-script, then that would be some more evidence supporting your point that /sbin/dhclient-script doesn't support virtual interfaces, as is. Patching the script seems more viable. The script does provide a lot of glue, but working around it as a debugging technique isolates what errors are coming from the script and what errors are coming from the program itself. I guess I was already pretty convinced that the source of the errors was ifconfig, given that the error can be reproduced external to dhclient and it's scripts by invoking ifconfig directly using the same arguments. The next questions is: is ifconfig broken, or is the manner in which dhclient is calling it broken? I don't believe patching the script will do you any good until the 'Bind socket to interface: No such device' error from dhclient is resolved... My assumption was that this was simply a side effect of the deconfigure step failing, which results in the virtual interface never being created, and thus dhclient has no device to work with. This can be resolved by either 1. patching the code so that it instantiates the virtual interface in a deconfigured state, or 2. special casing virtual interfaces so that the physical interface gets used for the DHCP handshake, while the specified virtual interface is used for the resulting call to ifconfig. (Apparently the latter happens with udhcpc.) Removing dhcp3-client (which removed ubuntu-minimal)... Removing ubuntu-minimal sounds like something to be avoided, but there was mention of people doing that (as a side effect of removing the wireless package) in the bug this one was split off from, and it didn't sound like it caused any problems. I'll have to take a look at ubuntu-minimal to see what it is. ...and installing dhcpcd worked just fine with /etc/network/interfaces ... and thus appears like a clean enough work around. Excellent. Thanks for the suggested workaround. Care to post the /etc/network/interfaces syntax you used for the virtual interface? (In my research I ran across about 3 or 4 variations.) -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Commenting on some of the comments in Bug #123773. In Bug #123773 Jamie Strandboge wrote: ...though ifup (and ifdown) will give that error, the interface comes up fine, and is pingable In this case the interface doesn't come up. In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/11 behemot wrote: ...that removing package wireless-tools...helps. Removing, moving, or disabling the execute bits on /etc/network/if-pre- up.d/wireless-tools seems to have no impact on this problem. In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/12 Alessandro Lo Forte wrote: I have located the problem in the file /etc/if-pre-up.d/wireless-tools... In fact the error code is generated when /sbin/ifconfig is invoked to bring up an alias (like eth0:0) interface. This suggests both problems likely have a common underlying cause. My research shows that /sbin/ifconfig, being invoked by dhclient, is also the culprit here. (See comments below.) This may also mean that this bug should be reclassified as being against the net-tools package instead of dhcp3. In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/22 Juuso Tähkäpää wrote: sudo ifconfig eth0:1 1.2.3.4 dhcpcd -I someid eth0:1 ...but still ifconfig shows no eth0:1. Manually assigned aliases (ifconfig eth0:2 $ip) do show up in ifconfig listings just as they should. Although I don't have dhcpcd installed, I've observed similar results with dhclient, where it fails to configure the interface, but invoking ifconfig directly with a static address works. This gives some hope for a possible workaround hack. I'm thinking in /etc/network/interfaces one could invoke a script using the 'up' argument for the main (real) interface, which then would invoke dhclient in some fashion or maybe using a simpler DHCP client like udhcpc that returns an IP address to a shell variable, and then invokes ifconfig, passing the address. It would have limitations, like requiring perpetual leases (I think, as there would be no process left running to handle an expired lease). In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/17 gumptravels wrote: ...makes me think that you may not be able use dhcp on virtual interfaces since the mac address would be the same as all the other virtual interfaces on that same parent, and the same as the parent itself. While a MAC address is often used as the default way to identify a DHCP client, the DHCP client can optionally supply other identifying information. For example, this theoretically correct (untested, due to this bug) stanza from /etc/network/interfaces specifies that when the DHCP client requests an address for the virtual interface that it identifies itself with the alternate host name, indianpoint. auto eth0:1 iface eth0:1 inet dhcp hostname indianpoint Being able to use DHCP on virtual interfaces is highly desirable in order to keep maintenance to a minimum, especially if you are using an integrated DHCP/DNS service, like Dnsmasq. In that case the act of requesting an address with the alternate host name will automatically generate a corresponding DNS A-record for that hast name. Thus DNS requires far less central administration. -Tom -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Forum threads relating to this issue: http://ubuntuforums.org/showthread.php?t=918015 http://ubuntuforums.org/showthread.php?t=515162 -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Attached is an archive containing the output of:
# strace -ff -F -o /tmp/dhclient.strace dhclient eth0:0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
SIOCSIFADDR: Permission denied
SIOCSIFFLAGS: Permission denied
SIOCSIFFLAGS: Permission denied
Bind socket to interface: No such device
Some interesting bits include:
From dhclient.strace.9271-avahi-autoipd:
execve(/usr/sbin/avahi-autoipd, [/usr/sbin/avahi-autoipd, -k, eth0:0],
[/* 7 vars */]) = 0
[...]
open(/var/run//avahi-autoipd.eth0:0.pid, O_RDWR) = -1 ENOENT (No such file or
directory)
write(2, Failed to kill daemon: No such f..., 48) = 48
write(2, \n, 1) = 1
exit_group(1) = ?
That avahi-autoipd is trying to access /var/run/avahi-autoipd.eth0:0.pid may be
by design, or may be a bug. I don't know enough about avahi to know whether it
normally has a separate daemon running for each interface, and if so, whether
that should apply to virtual interfaces.
I saw a similar error in some of the messages output by dhclient, where
it was trying to create a PID file for itself that incorporated the
virtual device name. Again, should it be running a separate instance of
the daemon for each virtual interface?
And from dhclient.strace.9272-ifconfig:
execve(/sbin/ifconfig, [ifconfig, eth0:0, inet, 0, up], [/* 7 vars
*/]) = 0
[...]
socket(PF_FILE, SOCK_DGRAM, 0) = 3
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
access(/proc/net/if_inet6, R_OK) = 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 6
[...]
ioctl(4, SIOCSIFADDR, 0xbfdbeb00) = -1 EACCES (Permission denied)
dup(2) = 7
fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(7, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 10), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f0b000
_llseek(7, 0, 0xbfdbe498, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(7, SIOCSIFADDR: Permission denied\n, 31) = 31
close(7)= 0
munmap(0xb7f0b000, 4096)= 0
ioctl(4, SIOCGIFFLAGS, {ifr_name=eth0:0,
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0
ioctl(4, SIOCSIFFLAGS, 0xbfdbe9e8) = -1 EACCES (Permission denied)
dup(2) = 7
fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(7, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 10), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f0b000
_llseek(7, 0, 0xbfdbe438, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(7, SIOCSIFFLAGS: Permission denied\n, 32) = 32
close(7)= 0
munmap(0xb7f0b000, 4096)= 0
ioctl(4, SIOCGIFFLAGS, {ifr_name=eth0:0,
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0
ioctl(4, SIOCSIFFLAGS, 0xbfdbe9e8) = -1 EACCES (Permission denied)
dup(2) = 7
fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(7, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 10), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f0b000
_llseek(7, 0, 0xbfdbe438, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(7, SIOCSIFFLAGS: Permission denied\n, 32) = 32
close(7)= 0
munmap(0xb7f0b000, 4096)= 0
exit_group(-1) = ?
This call to ifconfig seems to be the source of the errors. I'm puzzled how you
can get an EACCES error on a newly created socket while running as root, if
SELinux or AppArmor isn't involved (as far as I'm aware).
If I run the above command directly:
# /sbin/ifconfig eth0:0 inet 0 up
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Sure enough, same results. Using 0.0.0.0 also fails, but substitute a
real IP address for the zero placeholder and we get:
# /sbin/ifconfig eth0:0 inet 192.168.0.210 up
# ifconfig
[...]
eth0:0Link encap:Ethernet HWaddr 00:04:61:4b:d1:33
inet addr:192.168.0.210 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:16
[...]
It seems the EACCES error is incorrect and misleading, and the call should
instead return an error indicating that the address is invalid.
I'm assuming dhclient is calling ifconfig in this fashion in order to
create the virtual device, and if successful, is going to go back after
obtaining an IP address via DHCP and update the interface.
I gather some internals in ifconfig or the kernel changed.
-Tom
** Attachment added: strace -ff -F -o /tmp/dhclient.strace dhclient eth0:0
http://launchpadlibrarian.net/24607967/dhclient.strace.zip
--
dhclient fails for
[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
Tormod Volden wrote: The seven first comments indicate that this is a harmless warning and that things otherwise work well. Later some people join in with various problems that are not necessarily due the warning. Please file new bugs for these different problems. This seems like a good suggestion. This bug deals with virtual interfaces triggering a SIOCSIFFLAGS: Cannot assign requested address warning, while still succeeding, and can be remedied by removing or patching the /etc/network/if-pre-up.d /wireless-tools file. I've created Bug #351378 to track the issue where DHCP fails to work for a virtual interface, when a DHCP client is used directly, or indirectly via the /etc/network/interfaces config file, and is unaffected by the /etc/network/if-pre-up.d/wireless-tools file. The two bugs may have a common underlying cause, but superficially they have different symptoms. -- 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias https://bugs.launchpad.net/bugs/123773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Commenting on some of the comments in Bug #123773. In Bug #123773 Jamie Strandboge wrote: ...though ifup (and ifdown) will give that error, the interface comes up fine, and is pingable In this case the interface doesn't come up. In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/11 behemot wrote: ...that removing package wireless-tools...helps. Removing, moving, or disabling the execute bits on /etc/network/if-pre- up.d/wireless-tools seems to have no impact on this problem. In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/12 Alessandro Lo Forte wrote: I have located the problem in the file /etc/if-pre-up.d/wireless-tools... In fact the error code is generated when /sbin/ifconfig is invoked to bring up an alias (like eth0:0) interface. This suggests both problems likely have a common underlying cause. My research shows that /sbin/ifconfig, being invoked by dhclient, is also the culprit here. (See comments below.) This may also mean that this bug should be reclassified as being against the net-tools package instead of dhcp3. In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/22 Juuso Tähkäpää wrote: sudo ifconfig eth0:1 1.2.3.4 dhcpcd -I someid eth0:1 ...but still ifconfig shows no eth0:1. Manually assigned aliases (ifconfig eth0:2 $ip) do show up in ifconfig listings just as they should. Although I don't have dhcpcd installed, I've observed similar results with dhclient, where it fails to configure the interface, but invoking ifconfig directly with a static address works. This gives some hope for a possible workaround hack. I'm thinking in /etc/network/interfaces one could invoke a script using the 'up' argument for the main (real) interface, which then would invoke dhclient in some fashion or maybe using a simpler DHCP client like udhcpc that returns an IP address to a shell variable, and then invokes ifconfig, passing the address. It would have limitations, like requiring perpetual leases (I think, as there would be no process left running to handle an expired lease). In comment https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773/comments/17 gumptravels wrote: ...makes me think that you may not be able use dhcp on virtual interfaces since the mac address would be the same as all the other virtual interfaces on that same parent, and the same as the parent itself. While a MAC address is often used as the default way to identify a DHCP client, the DHCP client can optionally supply other identifying information. For example, this theoretically correct (untested, due to this bug) stanza from /etc/network/interfaces specifies that when the DHCP client requests an address for the virtual interface that it identifies itself with the alternate host name, indianpoint. auto eth0:1 iface eth0:1 inet dhcp hostname indianpoint Being able to use DHCP on virtual interfaces is highly desirable in order to keep maintenance to a minimum, especially if you are using an integrated DHCP/DNS service, like Dnsmasq. In that case the act of requesting an address with the alternate host name will automatically generate a corresponding DNS A-record for that hast name. Thus DNS requires far less central administration. -Tom -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Forum threads relating to this issue: http://ubuntuforums.org/showthread.php?t=918015 http://ubuntuforums.org/showthread.php?t=515162 -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
PetyrRahl wrote: If for some reason the network goes down, I have to remember to manually bring up eth0:0 otherwise my site is unaccessible for my external clients. I believe that symptom is addressed in Bug #95968. -- 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias https://bugs.launchpad.net/bugs/123773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
Attached is an archive containing the output of:
# strace -ff -F -o /tmp/dhclient.strace dhclient eth0:0
There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
SIOCSIFADDR: Permission denied
SIOCSIFFLAGS: Permission denied
SIOCSIFFLAGS: Permission denied
Bind socket to interface: No such device
Some interesting bits include:
From dhclient.strace.9271-avahi-autoipd:
execve(/usr/sbin/avahi-autoipd, [/usr/sbin/avahi-autoipd, -k, eth0:0],
[/* 7 vars */]) = 0
[...]
open(/var/run//avahi-autoipd.eth0:0.pid, O_RDWR) = -1 ENOENT (No such file or
directory)
write(2, Failed to kill daemon: No such f..., 48) = 48
write(2, \n, 1) = 1
exit_group(1) = ?
That avahi-autoipd is trying to access /var/run/avahi-autoipd.eth0:0.pid may be
by design, or may be a bug. I don't know enough about avahi to know whether it
normally has a separate daemon running for each interface, and if so, whether
that should apply to virtual interfaces.
I saw a similar error in some of the messages output by dhclient, where
it was trying to create a PID file for itself that incorporated the
virtual device name. Again, should it be running a separate instance of
the daemon for each virtual interface?
And from dhclient.strace.9272-ifconfig:
execve(/sbin/ifconfig, [ifconfig, eth0:0, inet, 0, up], [/* 7 vars
*/]) = 0
[...]
socket(PF_FILE, SOCK_DGRAM, 0) = 3
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
access(/proc/net/if_inet6, R_OK) = 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 6
[...]
ioctl(4, SIOCSIFADDR, 0xbfdbeb00) = -1 EACCES (Permission denied)
dup(2) = 7
fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(7, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 10), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f0b000
_llseek(7, 0, 0xbfdbe498, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(7, SIOCSIFADDR: Permission denied\n, 31) = 31
close(7)= 0
munmap(0xb7f0b000, 4096)= 0
ioctl(4, SIOCGIFFLAGS, {ifr_name=eth0:0,
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0
ioctl(4, SIOCSIFFLAGS, 0xbfdbe9e8) = -1 EACCES (Permission denied)
dup(2) = 7
fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(7, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 10), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f0b000
_llseek(7, 0, 0xbfdbe438, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(7, SIOCSIFFLAGS: Permission denied\n, 32) = 32
close(7)= 0
munmap(0xb7f0b000, 4096)= 0
ioctl(4, SIOCGIFFLAGS, {ifr_name=eth0:0,
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0
ioctl(4, SIOCSIFFLAGS, 0xbfdbe9e8) = -1 EACCES (Permission denied)
dup(2) = 7
fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(7, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 10), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f0b000
_llseek(7, 0, 0xbfdbe438, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(7, SIOCSIFFLAGS: Permission denied\n, 32) = 32
close(7)= 0
munmap(0xb7f0b000, 4096)= 0
exit_group(-1) = ?
This call to ifconfig seems to be the source of the errors. I'm puzzled how you
can get an EACCES error on a newly created socket while running as root, if
SELinux or AppArmor isn't involved (as far as I'm aware).
If I run the above command directly:
# /sbin/ifconfig eth0:0 inet 0 up
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Sure enough, same results. Using 0.0.0.0 also fails, but substitute a
real IP address for the zero placeholder and we get:
# /sbin/ifconfig eth0:0 inet 192.168.0.210 up
# ifconfig
[...]
eth0:0Link encap:Ethernet HWaddr 00:04:61:4b:d1:33
inet addr:192.168.0.210 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:16
[...]
It seems the EACCES error is incorrect and misleading, and the call should
instead return an error indicating that the address is invalid.
I'm assuming dhclient is calling ifconfig in this fashion in order to
create the virtual device, and if successful, is going to go back after
obtaining an IP address via DHCP and update the interface.
I gather some internals in ifconfig or the kernel changed.
-Tom
** Attachment added: strace -ff -F -o /tmp/dhclient.strace dhclient eth0:0
http://launchpadlibrarian.net/24607967/dhclient.strace.zip
--
dhclient fails for
[Bug 351378] [NEW] dhclient fails for virtual interfaces (IP aliases)
Public bug reported: dhcp3-client 3.0.6.dfsg-1ubuntu9 on Ubuntu 8.04 fails as follows when you attempt to use it to configure a virtual interface: # dhclient eth0:0 There is already a pid file /var/run/dhclient.pid with pid 134519072 Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ SIOCSIFFLAGS: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address Bind socket to interface: No such device This is a regression from the prior Ubuntu release, so I've read. Many supporting comments for this bug can be found in related bug #123773. ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 351378] [NEW] dhclient fails for virtual interfaces (IP aliases)
Public bug reported: dhcp3-client 3.0.6.dfsg-1ubuntu9 on Ubuntu 8.04 fails as follows when you attempt to use it to configure a virtual interface: # dhclient eth0:0 There is already a pid file /var/run/dhclient.pid with pid 134519072 Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ SIOCSIFFLAGS: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address Bind socket to interface: No such device This is a regression from the prior Ubuntu release, so I've read. Many supporting comments for this bug can be found in related bug #123773. ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329053] Re: Cannot use both zlib.output_compression and output_handler together!!
Kees Cook wrote: ...old installs of mythweb that contain a left-over copy of /etc/mythtv/mythwweb-htaccess file (it should be renamed to something else) So to clarify, this changes the steps to implement the workaround. I reverted the changes I had made to /etc/apache2/sites- available/mythweb.conf (per the prior comments), restarted apache, confirmed the problem was still present, then ran: # mv /etc/mythtv/mythweb-htaccess /etc/mythtv/mythweb-htaccess.obsolete # /etc/init.d/apache2 restart and that also worked to resolve the problem. Presumably mythweb-htaccess can then be deleted. -- Cannot use both zlib.output_compression and output_handler together!! https://bugs.launchpad.net/bugs/329053 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 338785] Re: Update to 3.0.7 breaks firefox
Added link to upstream bug. To summarize the upstream ticket, the problem is a side effect of the version upgrade process. Restarting FF will work around the problem. I'd infer from that, that the problem lies in the packaging, and not with the upstream project. One of the duplicate tickets here contains a developer comment stating that this isn't an easy problem to resolve. Although the current upgrade process does include a user notification that a FF restart is required, maybe a stop-gap solution would be to make that notification more forceful and intrusive, prompting the user to restart FF immediately before continuing to use it. ** Bug watch added: Mozilla Bugzilla #457434 https://bugzilla.mozilla.org/show_bug.cgi?id=457434 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=457434 Importance: Unknown Status: Unknown -- Update to 3.0.7 breaks firefox https://bugs.launchpad.net/bugs/338785 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299393] Re: Firefox crashes when trying to enter an address and on startup, too
John Vivirito wrote: That is a restart issue not the same as upstream bug. I'm confused then. Have you experienced this bug? What are the conditions under which it occurs. As far as what is described in this ticket, the symptoms are identical to what I have observed. Is it not resolved via a restart? Marking as invalid. If you are stipulating that this is a different bug from the upstream bug, then why is it invalid? If you see a different problem please report a separate bug report. Seems identical to me, but I've moved my comments and the reference to the upstream ticket over to Bug #338785. -- Firefox crashes when trying to enter an address and on startup, too https://bugs.launchpad.net/bugs/299393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329053] Re: Cannot use both zlib.output_compression and output_handler together!!
Kees Cook wrote: ...old installs of mythweb that contain a left-over copy of /etc/mythtv/mythwweb-htaccess file (it should be renamed to something else) So to clarify, this changes the steps to implement the workaround. I reverted the changes I had made to /etc/apache2/sites- available/mythweb.conf (per the prior comments), restarted apache, confirmed the problem was still present, then ran: # mv /etc/mythtv/mythweb-htaccess /etc/mythtv/mythweb-htaccess.obsolete # /etc/init.d/apache2 restart and that also worked to resolve the problem. Presumably mythweb-htaccess can then be deleted. -- Cannot use both zlib.output_compression and output_handler together!! https://bugs.launchpad.net/bugs/329053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326850] Re: Cannot use the address bar.It shows me a problem
*** This bug is a duplicate of bug 299393 *** https://bugs.launchpad.net/bugs/299393 ** This bug has been marked a duplicate of bug 299393 Firefox crashes when trying to enter an address and on startup, too -- Cannot use the address bar.It shows me a problem https://bugs.launchpad.net/bugs/326850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301021] Re: engine has no file! thrown after recent update
*** This bug is a duplicate of bug 299393 *** https://bugs.launchpad.net/bugs/299393 ** This bug has been marked a duplicate of bug 299393 Firefox crashes when trying to enter an address and on startup, too -- engine has no file! thrown after recent update https://bugs.launchpad.net/bugs/301021 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252311] Re: Firefox 3.0 crashes when input words in searchbar.
*** This bug is a duplicate of bug 299393 *** https://bugs.launchpad.net/bugs/299393 ** This bug has been marked a duplicate of bug 299393 Firefox crashes when trying to enter an address and on startup, too -- Firefox 3.0 crashes when input words in searchbar. https://bugs.launchpad.net/bugs/252311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338785] Re: Update to 3.0.7 breaks firefox
This is a dupe of Bug #299393. I'd mark it as such, but apparently I don't have adequate privileges to do that, given that several other bugs are marked as duplicates of this one. -- Update to 3.0.7 breaks firefox https://bugs.launchpad.net/bugs/338785 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299393] Re: Firefox crashes when trying to enter an address and on startup, too
** Bug watch added: Mozilla Bugzilla #457434 https://bugzilla.mozilla.org/show_bug.cgi?id=457434 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=457434 Importance: Unknown Status: Unknown -- Firefox crashes when trying to enter an address and on startup, too https://bugs.launchpad.net/bugs/299393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
