This happened while upgrading from 14.04 to 15.10 and then to 16.04 --
all on the same day of upgrades. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
Public bug reported:
Apparently caused by upgrade from 15.10 to 16.04.
sudo apt-get install --reinstall libvo-aacenc0:amd64 https://bugs.launchpad.net/bugs/1575752
Title:
package libvo-aacenc0:amd64 0.1.3-1 failed to install/upgrade: package
libvo-aacenc0:amd64 is already installed and
Same issue here on XPS 15-9530. I fixed it by switching to the nvidia
364 drivers from the graphics driver ppa:
sudo apt-get purge nvidia-361
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install nvidia-364
A full system restart (twice for some reason, power
Yeah i agree, there needs to be better documentation on the requirements
before installation of Unity8.
Great to to see the nvidia drivers are coming soon.
I will keep updating if i find something new.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Want to mention my struggle to get Unity8 working up up until now. I
still cant install apps but i got a lot of issues:
First Issues,
Login Screen - as soon as i hit enter to login the login box disappeared
and nothing else was happening, after 48 hours of research i realised i
was using nVidia
Hi Jamie - whatever you think is the best approach to have this work out
of the box for other Ubuntu users installing NTP and setting up a PPS
device. All I care about is that they don't have to edit apparmor
profiles themselves.
Mark
--
You received this bug notification because you
Public bug reported:
Am trying to get NTP to work with the kernel PPS subsystem, for high-
accuracy GPS-based clocks. On startup of NTPd I see this:
Apr 1 11:18:58 doorway kernel: [ 300.387443] audit: type=1400
audit(1459505938.042:9): apparmor="DENIED" operation="open"
Cannot install Hipchat either
W: Failed to fetch https://atlassian.artifactoryonline.com/atlassian
/hipchat-apt-client/dists/xenial/Release No Hash entry in Release file
/var/lib/apt/lists/partial/atlassian.artifactoryonline
.com_atlassian_hipchat-apt-client_dists_xenial_Release, which is
Is there a way to force my system to accept these keys anyway? I'd much
prefer to be warned that this is using a less secure hash rather than
being blocked from accessing these repos.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
The issue comes from insufficient boot disk space.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.19.0-51-generic 3.19.0-51.58~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
Uname: Linux 3.19.0-51-generic x86_64
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1555147
Title:
package
On Tue, Mar 01, 2016 at 08:09:59AM -, bugproxy wrote:
> --- Comment From ravi.bango...@in.ibm.com 2016-03-01 03:09 EDT---
> Hi Mark,
>
> > > * Fix finding the debug info for Ubuntu kernels (Mark Wielaard). LP:
> > > #1537125.
> >
> > Just a
On Wed, Feb 24, 2016 at 07:57:55AM -, Launchpad Bug Tracker wrote:
> This bug was fixed in the package elfutils - 0.165-3ubuntu1
>
> ---
> elfutils (0.165-3ubuntu1) xenial; urgency=medium
>
> * Fix finding the debug info for Ubuntu kernels (Mark Wielaard). LP:
Can we please get the extra devices into the pin code database.
is still missing in 15.10 (Wily). It is tedious to fix this every 6
months or so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
ime server. Please could we enable the PPS driver
in Ubuntu's build of NTP?
http://doc.ntp.org/4.2.6/drivers/driver22.html
Thanks,
Mark
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+subscriptions
--
Mailing list: https://launchpad.
Just hit this bug in Kubuntu 16.04. Removing some old gpg files seems to
have fixed it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1263540
Title:
Apt-get reports NO_PUBKEY
Sorry, meant to say 15.10 in the above comment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1263540
Title:
Apt-get reports NO_PUBKEY gpg error for keys that are present in
Public bug reported:
UK keyboard is NOT available as an input method in uBuntu 14.04 LTS ibus
(1.5.5-1ubuntu3) input method selection.
Please can someone fix this omission by adding the appropriate info to
/usr/share/ibus/component/simple.xml as having the system incorrectly
default to a US
Same problem here, on dell XPS15 9530 (512GB SSD, only seems to be
happening to the home partition.) 15.10 64 bit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1504688
PPS driver
in Ubuntu's build of NTP?
http://doc.ntp.org/4.2.6/drivers/driver22.html
Thanks,
Mark
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to
Public bug reported:
The first thing that happened after logging into Ubuntu 16.04 Alpha 1.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-2-generic 4.3.0-2.11
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mark 2186 F pulseaudio
/dev/snd/controlC0: mark 2186 F pulseaudio
Date: Fri Dec 18 13:13:47 2015
DuplicateSignature:
package:linux-image-3.13.0-73-generic:3.13.0-73.116:run-parts
sed for the sort so 8x13 - 8x18 resolutions
used by console fonts, and of course there is no such thing as hinting.
Can anybody else weigh on on the merits?
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-fam
Public bug reported:
ubuntu won't update
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
Uname: Linux 3.19.0-39-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
ApportVersion:
Public bug reported:
freezes when trying to load and shut down. Have to start in recovery
mode
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
Uname: Linux 3.19.0-39-generic i686
In Bug #1521771, I spent some time tracking down different behavior
between the mysql-5.5 "init" and "upstart" scripts. They differ on how
many seconds are waited between the SIGTERM and SIGKILL signals are
sent. Different values can mean the difference between a slower clean
shutdown and a
*** This bug is a duplicate of bug 333826 ***
https://bugs.launchpad.net/bugs/333826
This bug still exists in 2015... The problem appears with Gtk+ theme. If
you change to another theme (e.g cleanlooks) this issue will disappear.
(See post #1)
My PC setup:
DISTRIB_ID=Ubuntu
Thank you Christian!
Let's go with 4.2.8 for all the obvious reasons, get it done in Ubuntu
and offer up the patch to Debian.
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net
Public bug reported:
font issue kept coming up on boot
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
.tmp.unity.support.test.0:
ApportVersion:
It looks like sudo 1.8.12 made it into 15.10 finally. Excellent. Apple
went the other route and locked the clock back down.
(https://support.apple.com/en-us/HT205031)
The CVE associated with this bug seems to be about the TZ (seen on
RedHat's security site:
The proposed update works for us. When is it likely to be released as we
don't want to do this on our production servers?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504781
This bug appears to be included in another:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1497688.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1505764
Title:
15.04 installation continued and completed despite unmet dependencies.
However, sudo was no longer recognizing commands.
~$ sudo shutdown -r now
The program 'shutdown' can be found in the following packages:
* systemd-sysv
* upstart-sysv
* molly-guard
Try: sudo apt-get install
~$ sudo
Public bug reported:
Steps to reproduce (using a docker container):
$ docker pull ubuntu:trusty
$ docker run --rm -it ubuntu:trusty /bin/bash
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
# apt-get update
# apt-get install python3.4
python3.4 is already the
Thank you @racb for taking the time to look into this and reassign it
correctly - apols for my clumsy assignment.
Dan @daniel-thewatkins - thanks dude.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
The ifupdown configuration is working for me now, so for me this has
been resolved.
I'm not sure what changed or when.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Same here, bug still occurs. The longer you leave your machine on, the
better chance you hit the bug.
This is with an nvidia gtx 980, compiz 0.9.12.1 and nvidia driver 352.30
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Perfect, the login now works as expected.
I did try changing the password and removing and recreating the password
on the "mark" account from the user accounts dialogue box before posting
the bug but it made no difference.
Thank you
Mark
On Sun, Sep 27, 2015, at 11:01 PM, Robert An
Public bug reported:
For a long time (from previous versions) on my system I had only one
user - Mark - with admin privileges, a password set and auto-login at
startup. At boot I went directly to the Mark desktop.
Now I add another user for my daughter - Carol - normal user but with no
password
I'm experiencing exactly the same thing as the other report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1485558
Title:
NetworkManager breaks vboxnet*
David,
That's not lubuntu, it's 1 (one) ubuntu 4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1495178
Title:
Failed to set wall message, ignoring: Message recipient
That's been so long ago now, it's not even applicable anymore.
On Wed, Sep 9, 2015 at 6:25 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Mark Faine, is their a crash file in /var/crash after this issue occurs?
>
> ** Tags removed: bios-outdated-204
New version sudo 1.8.9p5-1ubuntu1.2 fixes the UID problem for me as well
on Trusty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1319403
Title:
uid match not working in
I have the same problem. I can't find anything that allows the use of a
remote printer (i.e. one shared by cups on another machine on the
network). Local system is cups 2.02, remote is cups 1.7.2 (Ubuntu
14.04).
--
You received this bug notification because you are a member of Ubuntu
Touch
Hi Simon
I have just received my Meizu phone and it's working seamlessly with my
Mazda Car entertainment system :)
Regards
mj
On 7 August 2015 at 19:21, Simon Fels simon.bu...@canonical.com wrote:
@Mark: You can. Follow https://wiki.ubuntu.com/DebuggingBluetooth to
generate logs
2015 at 11:21, Simon Fels simon.bu...@canonical.com wrote:
@Pat: Thanks for the pointer.
@Mark: How should reverse engineering help here? Its simply an
interoperability issue and we're using completely different software
than Android does. However the interface to the BT chip is standardized
so
OK thanks. I'll try it out tomorrow and revert back with
screenshots.
Regards
mj
On 7 August 2015 at 19:21, Simon Fels simon.bu...@canonical.com wrote:
@Mark: You can. Follow https://wiki.ubuntu.com/DebuggingBluetooth to
generate logs with debugging statements and then please attach them
The strange thing is that both the Samsung GS4 and the GS5 I owned before
always connected seamlessly. My BQ Aquaris is a different story, though. I
had once suggested that Canonical uses reverse engineering to solve this
issue, but I never received any feedback :(
Regards
mj
On 5 August 2015
Man, this is a favourite bug of mine, would be DELIGHTED to see a fix in
Wily ;)
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/762349
Title:
Difficult
I suspect this bug has aged out of existence now...bit disappointing to
see now *actual* updates to reflect progress mind you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
...*no* updates was what I meant to say.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/311637
Title:
dmraid enabled on install target even if disabled during
This bug happens whenever opening any application. workaround on
disabling unknown monitor in system settings seems to work temporarily
but needs to be done on every boot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus
** Package changed: app-install-data-partner (Ubuntu) = robolinux
** Changed in: robolinux
Status: Triaged = Fix Released
** Changed in: robolinux
Assignee: (unassigned) = MARK MORELOS (mightymouse777-777s)
--
You received this bug notification because you are a member of Ubuntu
Thanks. As I said, my BQ doesn't connect at all :( I really hope that this
is resolved ASAP
Regards
mj
On 8 July 2015 at 19:42, Dadio domini...@ramaekers-stassart.be wrote:
Confirm...
With a Meizu phone, this is also an issue.
The phone connects with my Audi carkit after a few tries. The
** Attachment removed: AlsaInfo.txt
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1458420/+attachment/4403767/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This is a blocking issue for users of iscsi-based storage HW on
Openstack; is there any way of re-prioritizing this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
*** This bug is a duplicate of bug 1390625 ***
https://bugs.launchpad.net/bugs/1390625
This is happening a lot to me
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1396361
christopher.m.penal...@gmail.com wrote:
Mark Faine, for regression testing purposes, could you please test
http://releases.ubuntu.com/trusty/ and advise to the results?
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1452519
Title
There seems to be some sort of misunderstanding. The bios was outdated
but it was 202 (I think) and now it is 204 but this is the most recent
version of the bios available.
The output of the command is:
N550JX.204
03/05/2015
The bios upgrade did change the behavior but it still crashes though
*** This bug is a duplicate of bug 1452519 ***
https://bugs.launchpad.net/bugs/1452519
I didn't have this laptop with any other versions of Ubuntu. It's new and
I installed Vivid straight out of the box.
On Sat, May 16, 2015, 12:00 PM Christopher M. Penalver
This problem has reappeared in 15.04 (Vivid Vervet). Symptoms exactly as
before.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744
Title:
MS Sculpt Touch Mouse needs
Does this help? Note it is the same mouse that originally gave problems
when this bug first appeared. It is also appearing twice in the list of
devices (there is only one).
Thanks,
Mark
mthornton@mark-PBL21:~$ bluez-list-devices
[ /org/bluez/863/hci0 ]
Address = 00:02:72:C6:AE:86
Powered
Working (for now). Pairing now survived a reboot.
Thanks,
Mark
On Friday, 15 May 2015, Marcos Alano 1094...@bugs.launchpad.net wrote:
Thanks Mark, help me so much. :)
The problem is in the Bluetooth device address: The prefix (which
indicates the manufacturer) is different for your mouse
Public bug reported:
Selecting logout takes several minutes before any action occurs and
there is no indication that the logout request was received by the OS.
Once it does decide to logout, I get a brief flash of a console
something about starting ACPI daemon then very quickly a black screen,
Public bug reported:
This happens at log out. Reboot and shutdown work fine but any attempt
to log out will freeze X. I can't even switch to a tty. The screen
freezes for about 30 seconds then drops to the shell but is still
frozen. The only way to correct the problem is a hard reboot.
You can set the time with:
timedatectl set-time 2000-01-01 10:00:00
Wow. Yeah, that'll make exploiting this *much* easier on desktop.
Fortunately Ubuntu Server doesn't allow this without authenticating.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Notice that only the SID changed though. That gives me a 1 in 32k
chance, and I can generate them basically at will with setsid. In my
testing so far, the inode of the TTY file for /dev/pts/0 has stayed 3
across several reboots. If it doesn't change, then it is moot from a
security standpoint.
To clarify: I reboot, log in, open gnome-terminal. The tty is always
/dev/pts/0, and ls -i /dev/pts/0 shows an inode of 3. This occurs even
if I shut down and power back on, though admittedly in a VM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Yup, I think so. while true; do setsid something to run sudo; done; or
the like. In my tests rolling through then all took about 5 minutes, and
that was in a crappy VM with 1 core and 30% CPU being used by compiz. I
haven't gotten it to pop an escalated shell yet, but I'll poke at it
more tonight
Without rebooting, the tty, inode, sid should change for every
terminal you open.
When I tried this on 15.04, the tty and inode didnt: only the SID
changed. Closing a gnome-terminal and reopening it got the same tty and
SID. For *additional* terminals, they got new ttys and inodes, but if
you
Oh, nevermind! You're talking about outside of the sudo instance. In the
case of Cron, etc: just let *the user* decide whether they want to be
asked after the first time. Make it an option to unlock the clock,
disabled by default but still available.
--
You received this bug notification because
Kay, the update to sudo (1.8.10) actually solves this by using the
monotonic clock. All that needs to happen is for Ubuntu to udpate to it.
:)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
Indeed. Trojaning those requires waiting for the user. Why lay a trap
and wait when you can just break down the door? If I can use dogtail or
similar to automate the clock and suddenly we're in drive-by territory.
--
You received this bug notification because you are a member of Ubuntu
Touch
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mark 1707 F pulseaudio
CurrentDesktop: Unity
Date: Wed Apr 29 14:49:48 2015
InstallationDate: Installed on 2011-08-24 (1344 days ago)
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5
Tyler,
it's great that this bug will be fixed. However, I have some concerns about the
mitigations factors.
1) Timestamp: Easily found in the auth.log, and easily bypassed due to
an unlocked clock.
2) TTY: The tty of the first gnome-terminal running is (as far as I can
tell) /dev/pts/0. That's
Congratulations, Ubuntu team. You have now fallen behind *Debian's
Stable Release* in a security update to sudo, despite several releases
in between. They even released their newest (24 month development cycle)
in the same month as you. This has been fixed, *fully fixed*, for over a
year now. Epic
Debian hasn't fixed this in squeeze or wheezy yet, it's fixed in
jessie because they have a recent enough version of sudo.
They haven't fixed it because they were never vulnerable: they don't
allow you to change the clock without a password.
We do plan on backporting monolithic timer support,
Really? If the terminal I last ran sudo in is open still on the machine,
and it's unlocked, I couldn't simply change the time back to the
previous sudo command an escalate?
Even if it's a remote chance, it's still an easy exploit.
/var/log/auth.log is certainly readable by a program that uses a
@Pilot6
quote:
...Return normal Ubuntu kernel and try again. Remove that 3.16.7 and
install...
I am looking for some generic solution cause, as I was saying (see #23),
I have Linux Arch x64 OS installed not ubuntu :) Anyways I am to try #12
instructions in combination with dkms
--
You
@Pilot6
I want to ask... The btusb version is 0.7
https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/tree/drivers/bluetooth/btusb.c?id=8f0c304c693c5a9759ed6ae50d07d4590dad5ae7
and the patch https://git.kernel.org/cgit/linux/kernel/git/next/linux-
@Pilot6
As I can see it, lsusb shows the bluetooth VID/PID values as 04ca:2006 (see
#15); But I don't get it how to find out correct *.hax with the info?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
@Pilot
OK... please give more details concerning how to find out which kernel version
must be running? I have kernel 3.16.7 so is it OK for #12 instructions or I
need another driver version?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
@Pilot6
So is the post #12 confirmed? I am to follow the instructions...
quote :
...Extract BCM43142A0_001.001.011.0122.0139.hex file from there...
I am not sure is the BCM43142A0_001.001.011.0122.0139.hex should be
exactly used for 04ca or there can be another *.hex version? I am asking
cause
@Pilot6
...I mean is there a way to compile the bluetooth module with make and then
use modprobe to post-insert the missing firmware bluetooth module into
already running kernel for example? I do need some generic solution cause
anyways it is the bluetooth driver issue not a OS-dependant one :)
@Pilot6
I mean that this patch has been applied to official Ubuntu kernel.
Sounds great; But is there the patch for www.kernel.org's non-compiled
kernels or is there a way to avoid re-compiling at all? I am asking
cause I have pre-compiled kernel 3.16.7 so I really want to fing some
generic
@Pilot6
I have bluetooth issue as well but I have Linux Arch OS (kernel 3.16.7);
Currently I coudn't find any Arch's os adapted solution so there is only way to
compile and install the standart www.kernel.org's kernel which is patched or
similar :) The bluetooth issue which described here (bug
Ack, thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1446256
Title:
Default out of the box menu option should be set to Global Menus
Status in Unity:
In Progress
I confirm this highly critical bug. The Today scope isn't visible
anymore after installing the update..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1446499
Do we need to take into account any overhead being added by the protocol
stack along the way?
For example, if the underlying MAAS machine can be told to use 9000 byte
MTUs and jumbo frames, then each layer up could adopt that, but might
need to chop off some of that for protocol / tunnel /
I also solved this in elementary Freya by installing xserver-xorg and
thereby reverting it to the Trusty version of the intel graphics stack.
So I would say it is a problem with the Utopic xserver drivers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Fix works for me. Thanks!
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1393542
Title:
[SRU] exfat not detected by blkid
Status in
Hi all :)
I have same broadcom bluetooth issue with my asus x551ma; The $usb-devices
outputs :
Vendor=04ca ProdID=2006 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM43142A0
S: SerialNumber=A4DB30BBDB48
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3
libsystemd-daemon.so.0 is a missing shared object that has pkgconfig
support and headers (sd-daemon.h). Why would all the dev support be
there, when the Shared Object is no where to be found?
please package this shared object. Why can Fedora 22/23 get this right,
but the Ubuntu+1 team can not?
Marty claims I can build it and I've seen freedesktop.org posts says I
can too if I have sd-daemon.c
Is sd-daemon.c the true source? I can't find this in any Vivid *.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Looking at system-219 from upstream now.
In order to build libsystemd-daemon.so.0, you need to configure like this:
./configure --enable-compat-libs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
here is the upstream tree
http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd/
sd-daemon.c is the source of interest
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
http://paste.ubuntu.com/10679310/
this is a compatibility package and is needed to build upstream xen 4.5.0 in
vivid 15.04
./configure --prefix=/usr --libdir=/usr/lib --enable-systemd --enable-ocamltools
** Affects: systemd (Ubuntu)
Importance: Undecided
Public bug reported:
slow
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Hi folks, this is a crash on startup that creates a bad impression of
the desktop. Is it a particularly complex fix?
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-location in
Ubuntu.
https
Tested and verified on PowerEdge R620 with trusty-proposed.
After updating and dist-upgrade, /dev/ipmi0 shows up as a device.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
301 - 400 of 437 matches
Mail list logo