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 ap
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 t
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 Ap
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:
iwlwi
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
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
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 i
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 2
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=tmpf
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, s
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 run
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), ('ha
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 ju
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.
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
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 reassig
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 g
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 d
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 scree
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
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,
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 / brightnes
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 rec
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
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 scre
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 necessar
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 d
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 Ubu
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 'deta
** 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 d
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
upgrad
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
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, whic
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:
di
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
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/122
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
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:
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
Titl
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
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:
disp
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:
di
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
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:
disp
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
Titl
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:
displa
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
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:
$ 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/i
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) st
** 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:
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 Inte
52 matches
Mail list logo
