@Thomas Mayer (thomas303)
Thanks. I don't want to file a new ticket because I think the problem is linked
to this one. But I try you patch No. 7, and after that I will see. Thank you
once more.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Installed gstreamer packages:
ii gstreamer1.0-alsa:amd64 1.10.3-1ubuntu1 amd64
GStreamer plugin for ALSA
ii gstreamer1.0-clutter-3.03.0.22-1 amd64
Clutter PLugin for GStreamer 1.0
ii gstreamer1.0-fluendo-mp3:amd64
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
yes. I purge driver of printer and reinstall it again. That all.
Everything ok.
03.02.2017 00:37, andrew buffa пишет:
> how do I fix?
>
> I now have no internet connection
>
> am using a backup pc
>
> Andrew
> On 1/31/2017 11:56 PM, rusbunker wrote:
>> Дмитрий добрый день! Я правильно понимаю
Public bug reported:
A few hours after upgrading to the latest kernel and plasma (using apt
upgrade) in Xenial 16.04LTS, my computer display hung with:
Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo:
write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS]
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
On Xubuntu 16.04.1 64bit. Switching to the brcmsmac wireless driver
seems to have fixed/significantly improved this issue for me. Using the
original bcmwl-kernel-source driver, bluetooth audio would cut out
completely during a network speedtest on wifi. With wifi off, bluetooth
sound would be
*** This bug is a duplicate of bug 167 ***
https://bugs.launchpad.net/bugs/167
** This bug has been marked a duplicate of bug 167
[snaps] License information from the store not available
--
You received this bug notification because you are a member of Desktop
Packages, which
** Description changed:
[Impact]
Update xserver to new minor release 1.18.4 in order to gain bugfixes from
upstream.
[Test case]
- Install and run, see that it's being used.
+ Install and run, check /var/log/Xorg.0.log that it's being used, and that
input/output works as they did with
In case anyone's interested, tried again after a recent Kernel Update
(Linux version 4.8.0-37-generic (buildd@lcy01-17) (gcc version 6.2.0
20161005 (Ubuntu 6.2.0-5ubuntu12) ) #39-Ubuntu SMP Thu Jan 26 02:27:07
UTC 2017 (Ubuntu 4.8.0-37.39-generic 4.8.16))
But same story on tty1 (This is not a log
Hello Dimitri, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.3-1ubuntu2.3~trusty1 in a few hours, and then
in the -proposed repository.
Please help
Already did, but just tried again. Still get login loop
According to what I've seen it's
304.134-0ubuntu1.16.10.1 not 304.134-0ubuntu0.16.10.1 that fixed the
problem in 16.04
Note the 0ubuntu1 not 0ubuntu0
If i try to load 304.134-0ubuntu1.16.10.1 I get this mesage E: Version
Seems to work fine for me on Zesty. Probably a missing gstreamer plugin.
Can you try installing these and then confirming whether it works?
gstreamer1.0-plugins-bad
gstreamer1.0-plugins-bad-faad
gstreamer1.0-plugins-bad-videoparsers
gstreamer1.0-plugins-base
gstreamer1.0-plugins-good
Please try this version of the package - 304.134-0ubuntu0.16.10.1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after update to
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1661448
Title:
failed fingerprint login behaviour confusing & ugly
I'm referring to the diagonal lines problem, like we see here and like is
documented here:
https://www.khronos.org/opengl/wiki/Common_Mistakes#Texture_upload_and_pixel_reads
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop
It could still be lack of glPixelStorei. In many cases the default
unpack alignment will be right by accident, so in those cases the text
will appear correct. It's possible that a different backend (X11 vs Mir)
creates a slightly different GL state and so the bug only appears in
some backends but
Example excerpt of a debian installer log:
Feb 3 00:31:15 pkgsel: starting tasksel
Feb 3 00:31:19 in-target: debconf: unable to initialize frontend: Passthrough
Feb 3 00:31:19 in-target: debconf: (Failed to open fd 3: Bad file descriptor
at (eval 19) line 3.)
Feb 3 00:31:19 in-target:
In addition this problem causes already installed machines to REMOVE
some packages on upgrade (when done using apt-get dist-upgrade)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
Public bug reported:
The latest xenial backports version of appstream has a breaks: gnome-
software (<< 3.22.5-1) in its control file, but there is no version of
gnome-software > 3.22 available in any xenial repos.
This causes the installation process to break when backports are
enabled.
**
@Kevin
NetworkManager already has code to monitor system signals related to
suspend/resume, so no adding additional scripts to /usr/lib/systemd
/system-sleep isn't the answer.
@Dan
Different bug... this bug is caused by NetworkManager's WiFi scanning
logic stalling due to a race condition.
yes the problem is in 16.10 Yakkety
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after update to nvidia 304.132
Status in
I just tried installing Nvidia again and still same login loop problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after
Ok, sorry. I thought Ubuntu Xenial was Ubuntu 16.10... but 16.10 is
Yakkety.
So the problem is in Ubuntu 16.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Just reread your message it's version 304.134-unbuntu1 that fixed the
problem in 16.104 not 304.132
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
What is availble in 16.10 is -0ubuntu0 not -0ubuntu1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after update to nvidia
Public bug reported:
Two problems:
1. Some attempts at printing a 20 page document from LibreOffice show
apparently reproducible output errors on particular pages (eg 3, 4, 8 etc) with
some lines 'smudged' but readable, some totally garbled, and others almost
correct.
2. With some attempts at
The versions of nvida-304 in 16.04 and 16.10. seem the same. They were
released on the same day and copied from the X staging PPA.
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Also affects: nvidia-graphics-drivers-304 (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-304 (Ubuntu Yakkety)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-304 (Ubuntu Yakkety)
Importance: Undecided => Critical
--
Failed swipe followed by success
** Attachment added: "fingerprint login - fail then success.png"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1661448/+attachment/4812284/+files/fingerprint%20login%20-%20fail%20then%20success.png
--
You received this bug notification because you
fingerprint login timeout (no swipe attempted)
** Attachment added: "fingerprint login - timeout .png"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1661448/+attachment/4812287/+files/fingerprint%20login%20-%20timeout%20.png
** Description changed:
When using fingerprint login,
Failed swipe then timeout
** Attachment added: "fingerprint login - failed swipe then timeout.png"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1661448/+attachment/4812285/+files/fingerprint%20login%20-%20failed%20swipe%20then%20timeout.png
--
You received this bug notification
Two failed swipes, then timeout. The password field is now hidden, but
still usable.
** Attachment added: "fingerprint login - 2 failed swipes then timeout (hidden
password field).png"
Public bug reported:
When using fingerprint login, the login display for a failed swipe followed by
a success looks rather ugly. Upon successful fingerprint, the login button is
not shown in full, but cut in half.
Two failed swipes followed by a successful swipe actually results in a non
@kgunn - yes I can reproduce it quite reliably too. No need to try the
glyph cache workaround thing, I checked it and it had no impact.
@duflu - Qt is rendering the text.
Since Qt renders text ok in Unity7, there must be some GL configuration
problem in QtMir/QtUbuntu causing this kind of issue.
Moreover, what I don't understand is why people said that they have the
version nvidia 304.134-0ubuntu0.16.04.1 in Ubuntu 16.10.
I have checked it, and in Ubuntu 16.10 the available version is this
one: 304.134-0ubuntu0.16.10.1 (note the difference in the lasts
digits).
Maybe both oh them are
Brian, nobody had said that the problem was solved for Ubuntu 16.10.
If you read their messages, they only said that the new version of the
driver (nvidia 304.134-0ubuntu0.16.10.1) is already published on the
repos.
However, when I install this new version, my computer don't login, so
the
I have
NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
with 16.10 nvidia-304 304.134-0ubuntu1 isn't available just nvidia-304
304.134-0ubuntu0 which still cause the login loop
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I agree it's not solved on 16.10
I believe there is an open bug about it on 16.10 but I can't find it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
It still seems to me than a set of features poorly designed. You can see
that by playing around with the two option: "--window" e "--tab"
a command like "gnome-terminal --window --tab" does exactly the same as
"gnome-terminal --tab --tab" but a different thing from "gnome-terminal
--window
Also affects me. I am using:
Operating System: Ubuntu 16.10
Kernel: Linux 4.8.0-34-generic
Dell XPS 15 9550
Sometimes it works, sometimes it doesn't. If I play with the alsa mixer
settings and pavucontrol I can get it to work. I've noticed that putting
the computer to sleep sometimes allows it
On Thu, Feb 02, 2017 at 10:44:32PM -, comu wrote:
> Please reopen the bug. The problem is not solved on Ubuntu 16.10
Could you provide some more information about how you tested and what
leads you believe that this not fixed. Plenty of people have
indicated, with details, that it works for
*** This bug is a duplicate of bug 1380364 ***
https://bugs.launchpad.net/bugs/1380364
Fixes are done in the development release at first hand, which at the
time for this fix was yakkety. I can confirm that it works on 16.10,
btw.
Whether to backport to one or more stable releases or not
Same issue with an ASUS ZenBook 3 UX390UA. I experience the issue as a
volume dependent cross-talk between the channels, predominantly
affecting the left channel when a medium volume sound is being played in
the right channel, but to a lesser extent (lower volume of the cross-
talk) affecting the
The output of "gnome-terminal --help" is probably a bit poorly worded.
The intent is that --tab opens a new tab in the window that was created
by a preceding --window option of this very same "gnome-terminal"
command line.
E.g.
gnome-terminal --window
--
You received this bug notification
(sorry, accidentally hit "Post")
E.g.
gnome-terminal --window --profile=asdf --tab --profile=qwer --tab
--profile=zxcv
Other than here, gnome-terminal does not keep track which of its windows
was the "last opened" (which may not even exist by that time, so it'd
need to be "most recent" instead,
Please reopen the bug. The problem is not solved on Ubuntu 16.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after update to
*** This bug is a duplicate of bug 1380364 ***
https://bugs.launchpad.net/bugs/1380364
Thanks for your prompt reply,
are you saying that normally a fix is applied only to the package version of
the current stable release and not to the package versions of the previous
supported releases
Public bug reported:
The kernel has a KMS driver for these since 2012 or so, and they should
use the fallback driver on X (modesetting).
** Affects: xserver-xorg-video-ast (Ubuntu)
Importance: Undecided
Status: New
** Affects: xserver-xorg-video-cirrus (Ubuntu)
Importance:
no, it's a separate source package used on 16.04.2 and up, this one is
for 16.04{,.1}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1639896
Title:
Backport support for AMD Polaris
*** This bug is a duplicate of bug 1514474 ***
https://bugs.launchpad.net/bugs/1514474
** This bug has been marked a duplicate of bug 1514474
package tex-common 6.04 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You received
Public bug reported:
User Agent: Mozilla 5.0 (X11; LinUX x86_64; rv:51.0) Gecko/20100101
Firefox/51.0.1
Build ID: 20170125172221
Steps to reproduce:
Opened HTML page https://www.cloudflare.com/; Opened Site Identity
Button
Reproducible: Always
Actual Results:
www.cloudflare.com
Connection
how do I fix?
I now have no internet connection
am using a backup pc
Andrew
On 1/31/2017 11:56 PM, rusbunker wrote:
> Дмитрий добрый день! Я правильно понимаю что если выполню инструкции
> прописанные в этом сообщении, я получу желаемое? А именно устновлю принтер.
>
>
> 31.01.2017 13:33,
Hi Balazs,
Do you still have this issue using Zesty and the last package of openchrome
(1:0.5.0-3)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-openchrome in
Ubuntu.
https://bugs.launchpad.net/bugs/1577573
Title:
Your syslog contains:
Feb 2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to
CUPS server; giving up
and you also get
@Eliot:~$ lpinfo -v
lpinfo: Bad file descriptor
Seems that there is a problem with the CUPS daemon not starting.
Please run the command
ls -l
xserver-xorg-video-amdgpu-hwe-16.04 (1.1.2-1~16.04.1) is in xenial-
proposed. Should it be dropped and replaced with this SRU?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1639896
@Gerry
I was going to try your suggestion, stop unity8 && start unity8
QML_USE_GLYPHCACHE_WORKAROUND=1. but it seems simply starting and stopping
unity8 is unhappy on zesty atm
fwiw, my current setup I'm seeing this 100%, and i agree cache seems
likely as first few windows are ok, but
Public bug reported:
Ubuntu 16.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-software
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: wl
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1661385
Title:
package tex-common 6.04 failed to install/upgrade: subprocess
installed
Public bug reported:
Update error
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Thu Feb 2 14:29:51 2017
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1661380
Title:
package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to
install/upgrade:
Public bug reported:
This error ocurred during an $> sudo apt upgrade -f
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-dev 2.48.1-1~ubuntu16.04.1
Uname: Linux 4.10.0-999-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Feb 2 18:04:59 2017
I installed im-config 0.29-1ubuntu16.2 from yakkety-proposed and
verified the test case.
** Tags removed: verification-needed
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
** Summary changed:
- Erro message when clicking "Windows Network" needs to be improved
+ Error message when clicking "Windows Network" needs to be improved
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Changed in: xorg-server-lts-xenial (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1586260
Title:
System freeze & no display if set
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libreoffice (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-lts-xenial (Ubuntu)
Status: New => Invalid
** Changed in: xorg-server-lts-xenial (Ubuntu Xenial)
Status: New => Invalid
** Also affects: xorg-server (Ubuntu
Regarding #69: This does not work at all. In resolv.conf there is still
nameserver 127.0.1.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1003842
Title:
dnsmasq sometimes
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-lts-xenial (Ubuntu)
Status: New => Invalid
** Changed in: xorg-server-lts-xenial (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug
On Yakkety there is no file /etc/NetworkManager/dnsmasq.d/strict-order.
Should a touch do the trick? If so why so?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1003842
Title:
*** This bug is a duplicate of bug 1380364 ***
https://bugs.launchpad.net/bugs/1380364
It was fixed in yakkety:
https://launchpad.net/ubuntu/+source/unity-control-
center/15.04.0+16.10.20161003.1-0ubuntu1
but not in xenial as it seems.
Marking this a duplicate of bug #1380364, then. (Can't
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-lts-xenial (Ubuntu)
Status: New => Invalid
** Changed in: xorg-server-lts-xenial (Ubuntu Xenial)
Status: New => Invalid
** Also affects: xorg-server (Ubuntu
** Changed in: xorg-server-lts-xenial (Ubuntu Xenial)
Status: New => Invalid
** Changed in: xorg-server-lts-xenial (Ubuntu Yakkety)
Status: New => Invalid
** Also affects: xorg-server (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects:
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xorg-server-lts-xenial (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xorg-server-lts-xenial (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-lts-xenial (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Bug #1443052 was fixed but this is still present
** This bug is no longer a duplicate of bug 1443052
User accounts login history showing incorrect history - patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center
Hello 林博仁, or anyone else affected,
Accepted im-config into yakkety-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/im-
config/0.29-1ubuntu16.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Tags added: ui
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/26472
Title:
Rhythmbox Freezes Upon WiFi Net Drop...
Status in Juniper Openstack:
In Progress
Status in Juniper
Looking at https://launchpad.net/ubuntu/+source/chromium-browser, I see
that 55.0.2883.87-0ubuntu2.1328 is currently in zesty-proposed but it
failed to build for some architectures.
** Tags added: upgrade-software-version zesty
--
You received this bug notification because you are a member of
The verification of the Stable Release Update for epiphany-browser has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package epiphany-browser - 3.18.10-0ubuntu1
---
epiphany-browser (3.18.10-0ubuntu1) xenial; urgency=medium
* New upstream bugfix release (LP: #1657284)
* Drop debian/patches/new_webkit_abi.patch, applied in new release
-- Jeremy Bicha
** Changed in: network-manager-openvpn (Ubuntu)
Assignee: (unassigned) => Martin Knudsen (proletar)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https://bugs.launchpad.net/bugs/360818
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
This bug was fixed in the package gst-plugins-bad1.0 - 1.8.3-1ubuntu0.2
---
gst-plugins-bad1.0 (1.8.3-1ubuntu0.2) xenial; urgency=medium
* Rebase on top of security update.
gst-plugins-bad1.0 (1.8.3-1ubuntu0.1) xenial; urgency=medium
* Backport from yakkety to 16.04 (LP:
This bug was fixed in the package gst-libav1.0 - 1.8.3-1ubuntu0.1
---
gst-libav1.0 (1.8.3-1ubuntu0.1) xenial; urgency=medium
* Backport from yakkety to 16.04 (LP: #1619600)
*
debian/patches/0001-Only-use-AV_CODEC_ID_WRAPPED_AVFRAME-on-new-enough-l.patch:
Take patch from
The verification of the Stable Release Update for gst-libav1.0 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package gst-plugins-good1.0 - 1.8.3-1ubuntu0.3
---
gst-plugins-good1.0 (1.8.3-1ubuntu0.3) xenial; urgency=medium
* Rebase on top of security update again.
gst-plugins-good1.0 (1.8.3-1ubuntu0.2) xenial; urgency=medium
* Rebase on top of security update.
This bug was fixed in the package gstreamer-vaapi - 1.8.3-1~ubuntu0.1
---
gstreamer-vaapi (1.8.3-1~ubuntu0.1) xenial; urgency=medium
* No-change backport to xenial (LP: #1619600)
gstreamer-vaapi (1.8.3-1) unstable; urgency=medium
* New upstream release.
-- Iain Lane
This bug was fixed in the package gstreamer1.0 - 1.8.3-1~ubuntu0.1
---
gstreamer1.0 (1.8.3-1~ubuntu0.1) xenial; urgency=medium
* No-change backport from yakkety to 16.04 (LP: #1619600)
gstreamer1.0 (1.8.3-1) unstable; urgency=medium
* New upstream bugfix release.
-- Iain Lane
This bug was fixed in the package gst-plugins-base1.0 - 1.8.3-1ubuntu0.1
---
gst-plugins-base1.0 (1.8.3-1ubuntu0.1) xenial; urgency=medium
* No-change backport from yakkety to 16.04 (LP: #1619600)
gst-plugins-base1.0 (1.8.3-1ubuntu1) yakkety; urgency=medium
* Merge from Debian
This bug was fixed in the package gst-plugins-ugly1.0 - 1.8.3-1ubuntu0.1
---
gst-plugins-ugly1.0 (1.8.3-1ubuntu0.1) xenial; urgency=medium
* No-change backport from yakkety to 16.04 (LP: #1619600)
gst-plugins-ugly1.0 (1.8.3-1ubuntu1) yakkety; urgency=medium
* Merge with Debian
Public bug reported:
Hi,
We install ubuntu/mint to numerous people and we got multiple
reports that the wifi password was not taken into account. We managed to
reproduce it by
1 - Select your wifi network
2 - Enter a fake password (Just to simulate a user error not entering well his
wifi
The verification of the Stable Release Update for epiphany-browser has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package epiphany-browser - 3.22.5-0ubuntu0.1
---
epiphany-browser (3.22.5-0ubuntu0.1) yakkety; urgency=medium
* New upstream bugfix release (LP: #1657258)
* Bump Build-Depends on libwebkit2gtk-4.0-dev to (>= 2.14.2) as per
configure.ac.
-- Jeremy
The verification of the Stable Release Update for gnome-online-accounts
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
This bug was fixed in the package gnome-online-accounts -
3.20.5-0ubuntu0.1
---
gnome-online-accounts (3.20.5-0ubuntu0.1) yakkety; urgency=medium
* New upstream bugfix release (LP: #1649995)
- Use a new Google API key because there are authentication errors
for anyone
Tested todays daily iso (2017-02-02), can't reproduce this bug.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
I have this installed: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
Is there a way to resolve these many critical failure messages by nautilus. I
get them whenever I start or close nautilus. See below:
Feb 2 23:41:59 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **:
1 - 100 of 117 matches
Mail list logo