[Bug 1593699] [NEW] build-depends should include dpkg >= 1.17
Public bug reported: Trying to backport 0.56ubuntu2 to precise fails with: dh_installdeb: unknown dpkg-maintscript-helper command: symlink_to_dir make: *** [binary-arch] Error 255 dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2 It looks like that appeared in dpkg 1.17 (precise has 1.16 supporting just rm_conffile and mv_conffile), so should be list in build-depends. ** Affects: java-common (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/1593699 Title: build-depends should include dpkg >= 1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1593699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571535] Re: iwlwifi restarts randomly in xenial
Having run with just the 2.4MHz network for a while, something still isn't right. Every so often the network just stops talking. NetworkManger still thinks its connected, but no traffic seems to pass. It logs nothing when this happens (I'm guessing it gets detected, though, as that would explain the 2.4 <-> 5 switching I was seeing before) I would suspect the router at this point, but another machine (with a different Intel chipset - lspci says Centrino Wireless-N 1030) never has any issues and, as mentioned originally, this only started after installing xenial, wily was fine. I'm out of ideas how how to try and debug this further. For reference I'm now using the 4.4.0-21-generic kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571535 Title: iwlwifi restarts randomly in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570759] Re: apt-get install juju does not install /usr/bin/juju
I do now have a /usr/bin/juju as expected. Thanks. $ ls -l /usr/bin/juju* lrwxrwxrwx 1 root root 8 Apr 19 10:31 /usr/bin/juju -> juju-2.0 lrwxrwxrwx 1 root root 9 Apr 20 01:40 /usr/bin/juju-1 -> juju-1.25 -rwxr-xr-x 1 root root 68 Apr 20 01:40 /usr/bin/juju-1.25 -rwxr-xr-x 1 root root 67 Apr 19 10:31 /usr/bin/juju-2.0 -rwxr-xr-x 1 root root 331 Mar 7 12:15 /usr/bin/juju-deployer lrwxrwxrwx 1 root root 45 Apr 20 08:30 /usr/bin/juju-run -> /home/chris/.juju/local/tools/machine-0/jujud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570759 Title: apt-get install juju does not install /usr/bin/juju To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1570759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571535] Re: iwlwifi restarts randomly in xenial
While I'm not sure why this only appeared in xenial, I've told network manager to prefer 2.4MHz for now in the hope that will help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571535 Title: iwlwifi restarts randomly in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571535] Re: iwlwifi restarts randomly in xenial
No change with an upstream kernel, I'm afraid. It lasted about 30 mins. $ uname -a Linux anduin 4.6.0-040600rc4-generic #201604172330 SMP Mon Apr 18 03:32:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux It did log something that I hadn't seen before, this time: Apr 19 10:01:27 anduin kernel: [ 23.775807] wlp1s0: authenticate with 00:8a:ae:c9:9a:d8 Apr 19 10:01:27 anduin NetworkManager[1023]: [1461056487.0028] device (wlp1s0): supplicant interface state: inactive -> authenticating Apr 19 10:01:27 anduin wpa_supplicant[1351]: wlp1s0: Trying to associate with 00:8a:ae:c9:9a:d8 (SSID='BTHub5-8KRS' freq=2437 MHz) ... Apr 19 10:28:45 anduin wpa_supplicant[1351]: wlp1s0: SME: Trying to authenticate with 00:8a:ae:c9:9a:d9 (SSID='BTHub5-8KRS' freq=5240 MHz) Apr 19 10:28:45 anduin kernel: [ 1662.238729] wlp1s0: disconnect from AP 00:8a:ae:c9:9a:d8 for new auth to 00:8a:ae:c9:9a:d9 Apr 19 10:28:45 anduin kernel: [ 1662.248214] wlp1s0: authenticate with 00:8a:ae:c9:9a:d9 Apr 19 10:28:45 anduin kernel: [ 1662.252410] wlp1s0: send auth to 00:8a:ae:c9:9a:d9 (try 1/3) Apr 19 10:28:45 anduin wpa_supplicant[1351]: wlp1s0: Trying to associate with 00:8a:ae:c9:9a:d9 (SSID='BTHub5-8KRS' freq=5240 MHz) So, it seems to be switching between the different network connections (first 2.4MHz then 5.2MHz) when it does this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571535 Title: iwlwifi restarts randomly in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571535] Re: iwlwifi restarts randomly in xenial
In the attached WifiSyslog.txt an example of this problem starts at "Apr 18 08:17:42" (followed by a network restart to get the vpn working again) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571535 Title: iwlwifi restarts randomly in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571535] [NEW] iwlwifi restarts randomly in xenial
Public bug reported: Recently installed xenial on a Lenovo Yoga 2-13 (Intel 7260 wifi card). On wily it worked perfectly, on xenial it regularly appears to restart the wifi connection (the end result is that I lose any vpn connections, as they don't seem to notice the restart, but that's another issue). In general use, I get periodic "wlp1s0: WPA: Group rekeying completed" messages in syslog (and used to get these in wily, too), but now, after a random amount of time (over the weekend it was several hours, this morning it was about 10 minutes, so it might be related to the amount of network traffic) I get "kernel: [13983.248157] wlp1s0: authenticate with 00:8a:ae:c9:9a:d8" (presumably my wifi router) and the usual wifi startup stuff including frequency lists, etc. It also always logs "systemd-udevd[30319]: Process '/sbin/crda' failed with exit code 249." every time (I'm not sure if this is relevant) After reading old, but similar bug reports, I've tried changing some of the module options: "11n_disable=1" and "11n_disable=8", but these had no effect. I've also tried the older firmware that wily used (/lib/firmware/iwlwifi-7260-13.ucode), but again, no improvement. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7058 F pulseaudio /dev/snd/controlC1: chris 7058 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 18 09:01:26 2016 HibernationDevice: RESUME=UUID=f92d915f-d552-4e5b-989d-70e936ce4f74 InstallationDate: Installed on 2016-04-14 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: LENOVO 20344 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN25WW(V1.11) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571535 Title: iwlwifi restarts randomly in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570773] [NEW] Xenial installer forgets it's not Debian
Public bug reported: Rather trivial, but the "force UEFI install" dialog thinks I'm installing Debian, not Ubuntu (see screenshots) The text is not very clear in the photo, but says "If you continue to install Debian in UEFI mode" This is from a xenial install from the latest (as of 14th April 2016) beta desktop iso ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "evidence" https://bugs.launchpad.net/bugs/1570773/+attachment/4637511/+files/screen.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570773 Title: Xenial installer forgets it's not Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1570773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559079] [NEW] swiftclient.service upload leaks filehandles for large files
Public bug reported: When uploading large files (i.e. multi-segment ones) using the swiftclient.service functions, if you pass a file path instead of a file object it seems to leave the files open after upload. For example: tmpfile = "/tmp/wibble" obj = SwiftUploadObject(tmpfile, object_name=tmpfile) swift.upload(container="mycontainer", objects=[obj]) After this, lsof shows /tmp/wibble is still open (multiple times) This approach works around the problem: with open(tmpfile, "r") as f: obj = SwiftUploadObject(f, object_name=tmpfile) swift.upload(container=container, objects=[obj]): While I've seen this on the wily packaged version, it also appears to be a problem in the upstream (3.0) python module. $ lsb_release -rd Description:Ubuntu 15.10 Release:15.10 $ apt-cache policy python-swiftclient python-swiftclient: Installed: 1:2.6.0-1ubuntu1 Candidate: 1:2.6.0-1ubuntu1 Version table: *** 1:2.6.0-1ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: python-swiftclient (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/1559079 Title: swiftclient.service upload leaks filehandles for large files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-swiftclient/+bug/1559079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559079] [NEW] swiftclient.service upload leaks filehandles for large files
Public bug reported: When uploading large files (i.e. multi-segment ones) using the swiftclient.service functions, if you pass a file path instead of a file object it seems to leave the files open after upload. For example: tmpfile = "/tmp/wibble" obj = SwiftUploadObject(tmpfile, object_name=tmpfile) swift.upload(container="mycontainer", objects=[obj]) After this, lsof shows /tmp/wibble is still open (multiple times) This approach works around the problem: with open(tmpfile, "r") as f: obj = SwiftUploadObject(f, object_name=tmpfile) swift.upload(container=container, objects=[obj]): While I've seen this on the wily packaged version, it also appears to be a problem in the upstream (3.0) python module. $ lsb_release -rd Description:Ubuntu 15.10 Release:15.10 $ apt-cache policy python-swiftclient python-swiftclient: Installed: 1:2.6.0-1ubuntu1 Candidate: 1:2.6.0-1ubuntu1 Version table: *** 1:2.6.0-1ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: python-swiftclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-swiftclient in Ubuntu. https://bugs.launchpad.net/bugs/1559079 Title: swiftclient.service upload leaks filehandles for large files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-swiftclient/+bug/1559079/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Hi Rafael,
I've been continuing Junien's investigations into this problem. The
machines have had all the BIOS and firmware updates I could find on HP's
website (although in the case of a DL385-G7 the latest appears to be
February 2014!) One of them only lasted a day before crashing again.
So, step 2 was to add "nox2apic intremap=off" to the DL385-G7s. I added
it to only one of them initially. That machine lasted 9 days before we
had another kernel panic ("NMI watchdog: BUG: soft lockup - CPU#27 stuck
for 23s! [migration/27:200]"), but after the panic it seems to have
settled back down again (without any reboot).
I've also added "intremap=no_x2apic_optout" to one of the DL360-G8s
after it crashed a couple of days ago. So far, it's doing ok.
I''m tempted to try upgrading them to linux-image-generic-lts-wily
(currently 4.2.0.18.13) unless there's any information from the current
setup that could be useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505564
Title:
Soft lockup with "block nbdX: Attempted send on closed socket" spam
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473908] [NEW] Clicking on external links when multiple firefox sessions running no longer works
Public bug reported: I usually have two firefox instances running, started as: firefox -P work firefox -P default --no-remote --new-window Up until the last update (39.0+build5-0ubuntu0.15.04.1) this worked fine. Now, clicking on a link (in, say Thunderbird) gives me the Firefox is already running, but not responding dialog. With just one instance running, clicking on a link still works, so it appears to be a problem with having more than one. Trying the above with -safe-mode has the same problem, so this is not extension-related. $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy firefox firefox: Installed: 39.0+build5-0ubuntu0.15.04.1 Candidate: 39.0+build5-0ubuntu0.15.04.1 Version table: *** 39.0+build5-0ubuntu0.15.04.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 37.0+build2-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ** Affects: firefox (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/1473908 Title: Clicking on external links when multiple firefox sessions running no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1473908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1435269] Re: System does not suspend when lid closed
journalctl -b output attached.
$ gdbus call --system -d org.freedesktop.login1 -o /org/freedesktop/login1 -m
org.freedesktop.login1.Manager.ListInhibitors
([('handle-power-key:handle-suspend-key:handle-hibernate-key', 'chris', 'GNOME
handling keypresses', 'block', uint32 1000, uint32 2444), ('handle-lid-switch',
'chris', 'Multiple displays attached', 'block', 1000, 2444), ('shutdown:sleep',
'Telepathy', 'Disconnecting IM accounts before suspend/shutdown...', 'delay',
1000, 3107), ('sleep', 'Unity Lockscreen', 'Unity wants to lock screen before
suspending.', 'delay', 1000, 2562), ('sleep', 'chris', 'GNOME needs to lock the
screen', 'delay', 1000, 2444), ('sleep', 'NetworkManager', 'NetworkManager
needs to turn off networks', 'delay', 0, 1006)],)
** Attachment added: Output of journalctl -b
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1435269/+attachment/4354304/+files/journalfile.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435269
Title:
System does not suspend when lid closed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1435269/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1435269] [NEW] System does not suspend when lid closed
Public bug reported: Under Utopic closing the laptop lid would suspend the system. Since a Vivid upgrade this no longer happens (the external screen goes blank for about a second, then the desktop comes back as before) The system power settings show When lid is closed: suspend as before, it just gets ignored. The menu suspend option does suspend correctly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:49:19 2015 InstallationDate: Installed on 2014-11-29 (113 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN25WW(V1.11) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435269 Title: System does not suspend when lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1435269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388880] [NEW] metadata update should not delete large file manifest
Public bug reported: If you upload a large file into swift using swift -S (or presumably the upload() method) then add extra metadata using swift post -m (or post_object()), the large file manifest metadata is deleted. It shouldn't do that. $ swift upload -S 1000 chrisstest /boot/initrd.img-3.16.0-22-generic boot/initrd.img-3.16.0-22-generic segment 3 boot/initrd.img-3.16.0-22-generic segment 0 boot/initrd.img-3.16.0-22-generic segment 1 boot/initrd.img-3.16.0-22-generic segment 2 /boot/initrd.img-3.16.0-22-generic $ swift stat chrisstest boot/initrd.img-3.16.0-22-generic Account: AUTH_06b6c15ea8c54b8f9832cbaf1fb6 Container: chrisstest Object: boot/initrd.img-3.16.0-22-generic Content Type: application/octet-stream Content Length: 30730085 Last Modified: Mon, 03 Nov 2014 14:51:20 GMT ETag: 235bbbe8ab0520eec94a6bb8cc079db6 Manifest: chrisstest_segments/boot/initrd.img-3.16.0-22-generic/1413445437.00/30730085/1000/ Meta Mtime: 1413445437.00 Accept-Ranges: bytes X-Timestamp: 1415026308.79456 $ swift post -m x-object-meta-test1:test1 chrisstest boot/initrd.img-3.16.0-22-generic $ swift stat chrisstest boot/initrd.img-3.16.0-22-generic Account: AUTH_06b6c15ea8c54b8f9832cbaf1fb6 Container: chrisstest Object: boot/initrd.img-3.16.0-22-generic Content Type: application/octet-stream Content Length: 30730085 Last Modified: Mon, 03 Nov 2014 14:53:52 GMT ETag: 53d3910d4f2cea329b515f19cbb5ca89 Meta X-Object-Meta-Test1: test1 Accept-Ranges: bytes X-Timestamp: 1415026432.67306 Interestingly, swift download (and the get_object() method) do re- create the segmented file correctly even without the manifest (does it just make an opportunistic look for chrisstest_segments?) System details: $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ apt-cache policy python-swiftclient python-swiftclient: Installed: 1:2.3.0-0ubuntu1 Candidate: 1:2.3.0-0ubuntu1 Version table: *** 1:2.3.0-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: swift (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/130 Title: metadata update should not delete large file manifest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/130/+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 1388880] [NEW] metadata update should not delete large file manifest
Public bug reported: If you upload a large file into swift using swift -S (or presumably the upload() method) then add extra metadata using swift post -m (or post_object()), the large file manifest metadata is deleted. It shouldn't do that. $ swift upload -S 1000 chrisstest /boot/initrd.img-3.16.0-22-generic boot/initrd.img-3.16.0-22-generic segment 3 boot/initrd.img-3.16.0-22-generic segment 0 boot/initrd.img-3.16.0-22-generic segment 1 boot/initrd.img-3.16.0-22-generic segment 2 /boot/initrd.img-3.16.0-22-generic $ swift stat chrisstest boot/initrd.img-3.16.0-22-generic Account: AUTH_06b6c15ea8c54b8f9832cbaf1fb6 Container: chrisstest Object: boot/initrd.img-3.16.0-22-generic Content Type: application/octet-stream Content Length: 30730085 Last Modified: Mon, 03 Nov 2014 14:51:20 GMT ETag: 235bbbe8ab0520eec94a6bb8cc079db6 Manifest: chrisstest_segments/boot/initrd.img-3.16.0-22-generic/1413445437.00/30730085/1000/ Meta Mtime: 1413445437.00 Accept-Ranges: bytes X-Timestamp: 1415026308.79456 $ swift post -m x-object-meta-test1:test1 chrisstest boot/initrd.img-3.16.0-22-generic $ swift stat chrisstest boot/initrd.img-3.16.0-22-generic Account: AUTH_06b6c15ea8c54b8f9832cbaf1fb6 Container: chrisstest Object: boot/initrd.img-3.16.0-22-generic Content Type: application/octet-stream Content Length: 30730085 Last Modified: Mon, 03 Nov 2014 14:53:52 GMT ETag: 53d3910d4f2cea329b515f19cbb5ca89 Meta X-Object-Meta-Test1: test1 Accept-Ranges: bytes X-Timestamp: 1415026432.67306 Interestingly, swift download (and the get_object() method) do re- create the segmented file correctly even without the manifest (does it just make an opportunistic look for chrisstest_segments?) System details: $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ apt-cache policy python-swiftclient python-swiftclient: Installed: 1:2.3.0-0ubuntu1 Candidate: 1:2.3.0-0ubuntu1 Version table: *** 1:2.3.0-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: swift (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/130 Title: metadata update should not delete large file manifest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1078213] Re: logs are not logrotated
As an interim solution:
juju deploy cs:~chris-gondolin/trusty/logrotate
juju set logrotate='logfiles={juju:{path:/var/log/juju/*.log}}'
On 02/10/14 08:38, Haw Loeung wrote:
ubuntu@juju-prod-XX-YYY-machine-0:/var/log/juju$ ls -la
total 19790064
drwxr-xr-x 2 syslog adm 4096 Oct 2 07:33 .
drwxr-xr-x 11 root root 4096 Oct 2 06:38 ..
-rw-r--r-- 1 syslog adm11719171973 Oct 2 07:33 all-machines.log.1
-rw--- 1 syslog syslog 879 Aug 18 20:17 ca-cert.pem
-rw-r--r-- 1 root root 1757 Oct 2 07:33 machine-0.log
-rw-r--r-- 1 root root8545817300 Oct 2 07:32 machine-0.log.1
-rw--- 1 syslog syslog 830 Aug 18 20:17 rsyslog-cert.pem
-rw--- 1 syslog syslog 887 Aug 18 20:17 rsyslog-key.pem
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1078213/+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
Re: [Bug 1078213] Re: logs are not logrotated
As an interim solution:
juju deploy cs:~chris-gondolin/trusty/logrotate
juju set logrotate='logfiles={juju:{path:/var/log/juju/*.log}}'
On 02/10/14 08:38, Haw Loeung wrote:
ubuntu@juju-prod-XX-YYY-machine-0:/var/log/juju$ ls -la
total 19790064
drwxr-xr-x 2 syslog adm 4096 Oct 2 07:33 .
drwxr-xr-x 11 root root 4096 Oct 2 06:38 ..
-rw-r--r-- 1 syslog adm11719171973 Oct 2 07:33 all-machines.log.1
-rw--- 1 syslog syslog 879 Aug 18 20:17 ca-cert.pem
-rw-r--r-- 1 root root 1757 Oct 2 07:33 machine-0.log
-rw-r--r-- 1 root root8545817300 Oct 2 07:32 machine-0.log.1
-rw--- 1 syslog syslog 830 Aug 18 20:17 rsyslog-cert.pem
-rw--- 1 syslog syslog 887 Aug 18 20:17 rsyslog-key.pem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1078213/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294547] [NEW] Screenshot shortcut keeps resetting
Public bug reported: I'm assuming compiz for this, since it's possibly related to #1284532. I use the print key to minimise windows, so I go to system settings / keyboard / shortcuts and tell the system to map print to minimise window. It says that's already used by screenshot, I click reassign reassign and all is well untilI restart the machine. After a restart it's been remapped so both minimise window and screenshot are assigned to the print key (screenshot always seems to win) Screenshot (or anything else) should not be automatically assigning itself once unassigned, especially to keys already assigned for other purposes. $ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 $ apt-cache policy compiz compiz: Installed: 1:0.9.11+14.04.20140310-0ubuntu1 Candidate: 1:0.9.11+14.04.20140310-0ubuntu1 Version table: *** 1:0.9.11+14.04.20140310-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: compiz (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/1294547 Title: Screenshot shortcut keeps resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1294547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1287666] Re: qemu-nbd processes left behind after instance deletion
On 07/03/14 10:03, James Page wrote: I've seen this happen when the server can't resolve its own hostname, resulting in extra output in the sudo commands that nova uses to create nbd devices; is that potentially happening in your case as well? Unless there was a temporary DNS glitch, this doesn't seem to be the case. The server can look up its own name happily and sudo doesn't show any unexpected output for me. Since it happened on more than one server at roughly the same time, while I can't find any evidence in the logs to support it, an external event (network glitch, busy firewall, etc.) is possible. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1287666 Title: qemu-nbd processes left behind after instance deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1287666/+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
Re: [Bug 1287666] Re: qemu-nbd processes left behind after instance deletion
On 07/03/14 10:03, James Page wrote: I've seen this happen when the server can't resolve its own hostname, resulting in extra output in the sudo commands that nova uses to create nbd devices; is that potentially happening in your case as well? Unless there was a temporary DNS glitch, this doesn't seem to be the case. The server can look up its own name happily and sudo doesn't show any unexpected output for me. Since it happened on more than one server at roughly the same time, while I can't find any evidence in the logs to support it, an external event (network glitch, busy firewall, etc.) is possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287666 Title: qemu-nbd processes left behind after instance deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1287666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417863] Re: bluetooth headset pairs but not available for audio
I'm seeing virtually the same behaviour under trusty on a headset that worked fine on raring (it was a bit iffy on saucy, but I think it eventually worked there too) This is a Plantronics ML10 headset. It pairs ok, gets listed in sound settings, but selecting it there has no effect and no sound gets directed to the headset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/417863 Title: bluetooth headset pairs but not available for audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/417863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284532] Re: print screen button appears hard-wired to screenshot
Sorry for picking the wrong package, here's the details for unity- control-center: $ apt-cache policy unity-control-center unity-control-center: Installed: 14.04.3+14.04.20140220.1-0ubuntu1 Candidate: 14.04.3+14.04.20140224-0ubuntu1 Version table: 14.04.3+14.04.20140224-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages *** 14.04.3+14.04.20140220.1-0ubuntu1 0 100 /var/lib/dpkg/status Since there's an update I'll try that to see if it fixes things, but at the moment a guest session behaves in exactly the same way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284532 Title: print screen button appears hard-wired to screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1284532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284532] Re: print screen button appears hard-wired to screenshot
It does, yes. Disabling screenshot to clipboard makes it work normally again. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284532 Title: print screen button appears hard-wired to screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1284532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284532] [NEW] print screen button appears hard-wired to screenshot
Public bug reported: After a recent update to Trusty, the print-screen button appears to be hard-wired to take a screenshot. In the keyboard shortcuts setup Take a screenshot is disabled (was print key), minimise window is set to the print key. Up until about two days ago, this worked fine, now these settings are ignored and pressing the print key makes the screenshot sound (no popup screenshot dialog, though) and the window is unchanged. $ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 $ apt-cache policy ubuntu-system-settings ubuntu-system-settings: Installed: (none) Candidate: 0.1+14.04.20140218.1-0ubuntu1 Version table: 0.1+14.04.20140218.1-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ** Affects: ubuntu-system-settings (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/1284532 Title: print screen button appears hard-wired to screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1284532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
No change I'm afraid. I might be misunderstanding what those options do, but the problem isn't the backlight itself. As I stated in the original bug report, changing the value in /sys/class/backlight/intel_backlight/brightness does dim the screen (as does the slider in system settings / brightness lock). The problem is that the brightness function keys (Fn+F4 and Fn+F5) stopped working after upgrading to Saucy. Somehow, what appears to be a keyboard issue seems to have morphed into hunting for a backlight-related problem (unless the two are more intertwined than I think) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
I've just tested the latest trusty-desktop-amd64.iso and it has the same problem. There's still no response to the brightness keys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
For my Trusty test it would not have been used (at least not intentionally), as that was from a pure live CD boot. For all other tests, it would be. Offhand, I don't recall why or when they were added, but I suspect it was an attempt to improve battery life or reduce the temperature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
Rather bizarrely, I can't get it to work with any of the mainline kernels. Even going back to 3.9.11-030911-generic which should work (since the real 3.10.0-6 works fine) I get no brightness control. I've also noticed the screen never seems to get turned off. After a while it will blank the screen, but the backlight is still on. This may be completely unconnected, but thought I'd mention it here just in case it may be relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
Trying bisecting didn't work for me, as (according to the wiki's translation of the output) it spans non-linear tags. My attempt to build from a 3.10 mainline kernel produced an image that suffered from the same issue, but that didn't provide a linux-image-extras package which seems to be necessary for the brightness controls to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
I've narrowed it down to 3.11.0-0.2 as the start of the problem. The last working saucy kernel was 3.10.0-6.17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
Latest kernel installed: $ uname -a Linux tuor 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Brightness keys still don't work and evtest still registers no keypresses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208838] Re: partial upgrade 'details' window does not fit on 768px high screen
Clicking on Details again does not make the window any smaller either, leaving a very large, mostly empty window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208838 Title: partial upgrade 'details' window does not fit on 768px high screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1208838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
Tested with linux-image-3.12.0-031200rc2-generic, but no change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] [NEW] display brightness keys stop working after saucy upgrade
Public bug reported: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) $ lsb_release -rd Description:Ubuntu Saucy Salamander (development branch) Release:13.10 $ apt-cache policy udev udev: Installed: 204-0ubuntu12 Candidate: 204-0ubuntu12 Version table: *** 204-0ubuntu12 0 500 http://gb.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: udev (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/1229591 Title: display brightness keys stop working after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: [keymap] display brightness keys stop working after saucy upgrade
$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Power Button /dev/input/event1: Sleep Button /dev/input/event2: Lid Switch /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Video Bus /dev/input/event6: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event7: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event8: HDA Intel PCH Headphone /dev/input/event9: HDA Intel PCH Mic /dev/input/event10: Dell WMI hotkeys /dev/input/event11: SynPS/2 Synaptics TouchPad /dev/input/event12: Laptop_Integrated_Webcam_HD Select the device event number [0-12]: 10 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: Dell WMI hotkeys Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 148 (KEY_PROG1) Event code 149 (KEY_PROG2) Event code 161 (KEY_EJECTCD) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 227 (KEY_SWITCHVIDEOMODE) Event code 236 (KEY_BATTERY) Event code 238 (KEY_WLAN) Event code 240 (KEY_UNKNOWN) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Testing ... (interrupt to exit) It displayed nothing when I pressed the keys. I also tried choosing event4 with the same result (or rather, lack of result) ** Attachment added: Output from udevadm info --export-db https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1229591/+attachment/3837828/+files/udev.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: [keymap] display brightness keys stop working after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
apport information ** Tags added: apport-collected ** Description changed: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) $ lsb_release -rd Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 $ apt-cache policy udev udev: Installed: 204-0ubuntu12 Candidate: 204-0ubuntu12 Version table: *** 204-0ubuntu12 0 500 http://gb.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status + --- + ApportVersion: 2.12.4-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: chris 2646 F pulseaudio + DistroRelease: Ubuntu 13.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2011-11-18 (675 days ago) + InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) + MachineType: Dell Inc. Dell System Inspiron N411Z + MarkForUpload: True + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=8bcbab07-7d4f-4c89-b6db-54aeed6ad1c4 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 + RelatedPackageVersions: + linux-restricted-modules-3.11.0-8-generic N/A + linux-backports-modules-3.11.0-8-generic N/A + linux-firmware1.114 + Tags: saucy + Uname: Linux 3.11.0-8-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago) + UserGroups: adm admin cdrom davfs2 dialout lpadmin plugdev sambashare + dmi.bios.date: 09/10/2012 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A06 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 0P01VP + dmi.board.vendor: Dell Inc. + dmi.board.version: FAB1 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0P01VP:rvrFAB1:cvnDellInc.:ct8:cvr0.1: + dmi.product.name: Dell System Inspiron N411Z + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837976/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837980/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837978/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837979/+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/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837981/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837977/+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/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837988/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837990/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837987/+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/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837984/+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/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837982/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837989/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837983/+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/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837985/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837986/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1229591/+attachment/3837991/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
Just tried with an older kernel, as suggested (3.8.0-30) and it brings the correct behaviour back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049314] Re: glance-registry package drops incorrect logrotate config
** Tags added: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049314 Title: glance-registry package drops incorrect logrotate config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1049314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375915] Re: It tooked 5 minutes for Evolution to open the Compose Message window. Evolution was unresponsive during that time.
I'm seeing the same thing, but it's not just limited to Evolution - I've also seen it when trying to open a new OpenOffice document and in FSpot (while adding tags to new photos I think). It started after upgrading to Jaunty from Intrepid for me. Similar setup to original reporter, but using Intel rather than Nvidia graphics, so no non-free modules. Sometimes (like now, when I'm trying to reproduce it) it will work fine, but once the problem happens it's there until the machine is restarted - every Compose operation takes several minutes before its useable. -- It tooked 5 minutes for Evolution to open the Compose Message window. Evolution was unresponsive during that time. https://bugs.launchpad.net/bugs/375915 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
