Given the Assignee: auto-github-vim-vim #851
I think what happened is that someone noticed this is also the bug in github.
However, if you read the bug in github, they closed *that* bug because they
said it was an Ubuntu bug. So I think there is no Fix Released, as upstream
said it was an Ubunt
Hello. I have experienced this bug after updating from Ubuntu 14 to Ubuntu 16
(it did not exist in Ubuntu 14).
Following what it is said in this thread, I have created an script in $HOME/bin
with the contents:
gnome-session-quit --logout --no-prompt
To logout, I open a terminal and execute this
I'm removing the direct remote watch as they said it is an Ubuntu bug.
** Changed in: vim
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611363
Title:
vim.gtk3 crash
Public bug reported:
Running Tomcat7 on Ubuntu 16.04 with Java7 gives an exception when
deploying apps.
Error: SEVERE: Context initialization failed
java.lang.NoSuchMethodError:
java.util.concurrent.ConcurrentHashMap.keySet()Ljava/util/concurrent/ConcurrentHashMap$KeySetView;
at
org.apache.
Public bug reported:
Installatio de filezilla échoue
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.4
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sun Dec 18
Public bug reported:
in the middle of the install, I don't have access to any additional logs
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Arch
Christopher M. Penalver, I had tested 4.9-r5, which gives a kernel panic at
boot. Now I've tested the latest mainline kernel 4.9. Kernel panic at boot, too.
How should I proceed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793141/+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/1650796
Title:
Black
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793142/+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/1650796
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793144/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16507
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793143/+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/1650796
Title:
apport information
** Tags added: apport-collected
** Description changed:
Problem was discovered on Dell 6400 laptop (32-bit) after upgrading Ubuntu
14.04 to 16.40.
Launching Cheese with Live! Cam Connect HD VF0750 webcam *sometimes*
(randomly) gives no video, only black image. No errors
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793145/+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/1650796
Title:
Blac
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793147/+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/1650796
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793146/+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/1650796
Title:
Blac
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793153/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650796
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793152/+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/1650796
Title:
Bl
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793149/+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/165
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793150/+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/1650796
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793148/+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/1650796
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1650796/+attachment/4793151/+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/1650796
Titl
In my case, as You can see in the photo, I can't forget a device even if
the bluetooth is on.
OTA14, krillin
Aquaris E4.5
Funny thing is that I can forget the other device from my list but never
any "Scania BT" which actually never connects.
** Attachment added: "image20161218_093810624.jpg"
However I also have another device which I'm able to forget only when BT
is on. Both devices I described here do not connect with the phone.
** Attachment added: "image20161218_095234795.jpg"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1535829/+attachment/4793155/+files/image20161218_
Public bug reported:
I can't forget some devices no matter whether BT is on or off (Bug #1535829).
There are two devices on my list at the moment: a car audio which I can't
forget no matter what I do
and a Garmin navigation device which I can forget only when BT is on.
Reported for krillin E4.5
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package libfm - 1.2.5-1ubuntu1
---
libfm (1.2.5-1ubuntu1) zesty; urgency=medium
* Merge from Debian unstable, Ubuntu remaining changes :
* debian/control:
- libfm-gtk-data breaks libfm-data, since images folder was misplaced in
previous revision.
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
This bug was fixed in the package imagemagick - 8:6.9.6.6+dfsg-1ubuntu3
---
imagemagick (8:6.9.6.6+dfsg-1ubuntu3) zesty; urgency=medium
* debian/patches/0020-Revert-GradientImage-change.patch: Revert patch
per https://github.com/ImageMagick/ImageMagick/issues/316. Thanks
to
Public bug reported:
This is important gameplay feature, and seems that this was changed by
somebody newer played mines, wasn't it so?
** Affects: gnome-mines (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Unable to play videos in firefox browser
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 50.1.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-105.152~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-105-generic x86_64
AddonCompatCheckDisabled: Fa
hello blancetnoir,
I cannot reproduce the error on Debian unstable, where the same version
of libjgoodies-animation-java (1.4.3-1) and of course the same jajuk
version is used.
Does it occur directly on startup?
It seems the fix is simple: Include jgoodies-common.jar in the MANIFEST
(as you writ
If a Ubuntu user/dev could confirm that building jajuk with jgoodies-common.jar
int the MANIFEST.MF fixes the problem, then I could _try_ to trigger a SRU.
Cheers and Best Regards,
Felix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-gevent (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560117
Title:
gevent 1.1 (non beta) released, please merge from Debian testing
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: otrs2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612617
Title:
[Fri
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
are sourceforge aware of the missing "%20" ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607535
Title:
ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts
and should be update
Public bug reported:
When using the newtexsf package in Ubuntu 16.10 I get the following
error:
(/usr/share/texlive/texmf-dist/tex/latex/newtxsf/omlntxsfmi.fd)
No file OMSntxsy.fd.
! LaTeX Error: This NFSS system isn't set up properly.
See the LaTeX manual or LaTeX Companion for explanation.
Ty
Public bug reported:
Update-manager told me:
"An unresolvable problem occurred while initializing the package information.
Please report this bug against the 'update-manager' package and include the
following error message:
E:can not open
/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_zest
*** This bug is a duplicate of bug 1620300 ***
https://bugs.launchpad.net/bugs/1620300
Thanks for reporting.
This is a duplicate of bug 1620300 which contains more information and
discussion. The good news is that a newer version of spyder has been
packaged for Ubuntu Zesty, and people are wo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: spyder (Ubuntu Yakkety)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620300
Titl
*** This bug is a duplicate of bug 1633737 ***
https://bugs.launchpad.net/bugs/1633737
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1633737, so it is being marked as such. Please look
This bug was fixed in the package node-jison - 0.4.17+dfsg-3build2
---
node-jison (0.4.17+dfsg-3build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Wed, 14 Dec 2016 01:57:41 -0500
** Changed in: node-jison (Ubuntu)
Status: New => Fix
Public bug reported:
Que dois je faire ?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Compiz
This bug was fixed in the package node-ebnf-parser - 0.1.10+dfsg-3build2
---
node-ebnf-parser (0.1.10+dfsg-3build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Wed, 14 Dec 2016 02:03:40 -0500
** Changed in: node-ebnf-parser (Ubuntu)
** Changed in: node-escodegen (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644894
Title:
node-jison needs bootstrapping
To manage notifications about t
Youtube also loses H264 support with the update:
Unpacking chromium-codecs-ffmpeg-extra (55.0.2883.87-0ubuntu0.16.10.1328) over
(53.0.2785.143-0ubuntu1.1307) ...
If you check youtube.com/html5 H264 is shown as not supported
--
You received this bug notification because you are a member of Ubunt
As mentioned above, I created a small debdiff for a rebuild of the
package for 16.04. It would still be really nice if someone could check
with the package in 16.10 whether that works as expected or if it would
need a similar fix. :)
** Patch added: "rebuild.debdiff"
https://bugs.launchpad.net
Public bug reported:
I made a bootable USB with Rufus,and I even made sure to check for bad blocks
in the USB and all was fine.
I then proceeded to install Lubuntu,but the installer crashed near the end of
the installation procedure.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquit
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640892
Title:
pbuilder: remove_packages() checks for existence in host, not in
Public bug reported:
After I boot Ubuntu 17.04 "Zesty Zapus" (dev)
$ systemd-resolve www.facebook.com
www.facebook.com: resolve call failed: DNSSEC validation failed:
failed-auxiliary
But after I have started Mozilla Firefox, and I try again it correctly
resolves.
$ systemd-resolve www.faceboo
>Que dois je faire ?
Using translate.google.com:
>What should I do ?
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to rep
Public bug reported:
According to the /usr/share/doc/fail2ban/README.Debian.gz:
`
* Enabled Sections:
Only handling of ssh files is enabled by default. If you want to use
fail2ban with apache, please enable apache section manually in
/etc/fail2ban/jail.local by including next lines:
[apache
This bug was fixed in the package node-lex-parser - 0.1.4-5build2
---
node-lex-parser (0.1.4-5build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Sun, 18 Dec 2016 05:35:09 -0500
--
You received this bug notification because you are a membe
Public bug reported:
https://www.xpra.org/trac/wiki/Versions says that there are only 2
supported versions, 0.14.x (supported until 2017 and backward compatible
with many old versions, including the version shipped in 14.04 LTS) and
1.0.x (supported for 2 more years). 0.15.x which ships with Ubunt
if you have compiled gr-osmosdr yourself and still nothing works then it
could be becase there's another lib installed in the /usr/lib/x86_64
-linux-gnu
solution:
sudo mv /usr/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.1.4
/usr/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.1.4.sav
sudo ln -s
Public bug reported:
>From the duplicate bug #1649011:
"When using the mouse to select multiple files in a GTK3 application via
the file chooser, everything works as expected, but if you undrag the
lasso, you just made to unselect them, once the last file is unselected,
the entire application cra
This bug was fixed in the package node-levn - 0.3.0+dfsg-1build2
---
node-levn (0.3.0+dfsg-1build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Sun, 18 Dec 2016 05:34:48 -0500
** Changed in: node-levn (Ubuntu)
Status: New => Fix Rele
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650879
Title:
Fi
*** This bug is a duplicate of bug 1650879 ***
https://bugs.launchpad.net/bugs/1650879
I personally reproduced this bug and let apport report bug #1650879.
Please subscribe and follow the other one. Thanks.
** This bug has been marked a duplicate of bug 1650879
File Chooser crashes GTK3 a
This bug was fixed in the package node-type-check - 0.3.2+dfsg-1build2
---
node-type-check (0.3.2+dfsg-1build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Sun, 18 Dec 2016 05:36:38 -0500
** Changed in: node-type-check (Ubuntu)
Statu
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1650879/+attachment/4793233/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650879
Title:
File Chooser
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1650879/+attachment/4793234/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650879
Title:
F
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1650879/+attachment/4793235/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1650879/+attachment/4793223/+files/CoreDump.gz
** Changed in: gtk+3.0 (Ubuntu)
Import
StacktraceTop:
g_assertion_message () from
/tmp/apport_sandbox_nFZ9oq/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from
/tmp/apport_sandbox_nFZ9oq/lib/x86_64-linux-gnu/libglib-2.0.so.0
_gtk_rbtree_node_find_offset (tree=, node=) at
/build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./g
Srijan Kumar Sharma, to be honest I thought about making separate bug
reports but I think maybe Linux kernel is sponsored by Intel or
something. Because all my bug reports related to machines with AMD
processors got silently ignored after making me collect information
after information. So I decide
Hopefully a final comment about this from me, with a suggestion about
how to restore the packages that you don't want from "proposed" back to
stable repository versions.
With some help from another Ubuntuforums member, 1fallen, I was given this info
page from askubuntu
http://askubuntu.com/questi
This bug was fixed in the package node-prelude-ls - 1.1.2+dfsg-2build2
---
node-prelude-ls (1.1.2+dfsg-2build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Sun, 18 Dec 2016 05:36:07 -0500
--
You received this bug notification because you a
** Bug watch added: Debian Bug tracker #835401
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835401
** Also affects: texlive-extra (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835401
Importance: Unknown
Status: Unknown
** Tags added: yakkety
--
You received t
This bug was fixed in the package node-optionator - 0.8.2+dfsg-1build2
---
node-optionator (0.8.2+dfsg-1build2) zesty; urgency=medium
* Revert to Debian packaging (LP: #1644894)
-- Jeremy Bicha Sun, 18 Dec 2016 05:35:40 -0500
** Changed in: node-optionator (Ubuntu)
Statu
1 - 100 of 492 matches
Mail list logo
