Public bug reported:
Running 'zmap' results in the following error: "zmap: error while
loading shared libraries: libjson-c.so.4: cannot open shared object
file: No such file or directory". It seems that it is built with
libjson-c4 instead of the new libjson-c5 that is available for Ubuntu
Jammy.
Public bug reported:
Just logged in, i opened Terminal ...
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: unity-settings-daemon 15.04.1+21.10.20210715-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion:
Okay! I think I solved it, in a way I didn't expect to.
So... Everytime I have to fix the standard booting to even be able to
get into Windows. That's the order in which I do things. Then, I try
dual boot installation with Ubuntu and it failed everytime. This time,
it failed again. On the grub
So I had another crash. Even though I thought I managed to fix grub this
time, before trying the Ubuntu install again.
I don't know why it's still doing this. But I kept having to switch
between CSM to try secureboot, and uefi and legacy settings for the
Ubuntu program boot-repair. But honestly
Public bug reported:
This started with me thinking I had created a surplus partition years
ago already when trying to set dual boot up Ubuntu + Windows 10. I got
it working, but I had my eye on this 530mb partition that I thought
wasn't supposed to be there.
But it stayed.
Now only recently, I
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: kerneloops 0.12+git20140509-6ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
Public bug reported:
I played around with certificates in docker containers earlier this day,
which should not have affected host configuration.
Now I was presented an update, which I started, resulting in a crash.
Description:Ubuntu 20.04.2 LTS
Release:20.04
ProblemType: Package
Public bug reported:
Installation breaks.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.41
ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18
Uname: Linux 4.15.0-126-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
It seems, that the installer thinks I'm on 17.10, while this is really 18.04
This is seen in os-release:
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
dmesg was not included in the bug report.
I now add it
** Attachment added: "Output from dmesg"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1907106/+attachment/5441653/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
1) Description: Ubuntu 20.04.1 LTS
Release: 20.04
2) ca-certificates:
Installiert: 20201027ubuntu0.20.04.1
Installationskandidat: 20201027ubuntu0.20.04.1
Versionstabelle:
*** 20201027ubuntu0.20.04.1 500
500 http://de.archive.ubuntu.com/ubuntu
a deb package of the
module for 18.04 https://github.com/phusion/nginx-modsecurity-ubuntu but it
is not maintained anymore.
Br Niels
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Made a quick video to illustrate the issues:
https://youtu.be/SwBtxqTqsHc
** Summary changed:
- Fractional scaling does not persist across reboots in resizable VM windows
+ Fractional scaling does not persist while resizing or rebooting in VM windows
--
You received this bug notification
Behaviour seems somewhat improved but the root issue is still there.
When rebooting with VMware Player running the scaling is now remembered
correctly, however if I then shut the VM down completely and restart it,
it still starts up at first in default screen size, removing the
scaling.
Also the
I can confirm this does seem to 'fix' the issue. At first the seamless
mouse gets in some "hybrid state" where I can move the mouse out of the
window, but the Ubuntu screen still shows it stuck at the corner. When I
then resize the screen it snaps back to normal behaviour. I suppose that
supports
Wayland doesn't work at all, hangs for 5+ minutes after login in VMware
(this reflects my experiences with Wayland on 18.04 and 18.10 in VMware,
don't think I've ever seen it work properly).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Considering that Mutter indeed knows that a monitor is virtual -
shouldn't it just ignore resolution completely for resolving existing
configuration? It changes all the time while dragging windows on the
host machine, maximizing, minimizing etc
--
You received this bug notification because you
One can easily reproduce this by running:
xrandr --output Virtual1 --scale 0.8x0.8
This will kill the seamless mouse directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885025
Title:
Thanks Daniel for referencing that comment, it's indeed also relevant
here.
It seems weird as a whole that the available scaling options appear to
depend on common monitor resolutions. As stated there at 3840x2075
(that's 4k minus the VMware window borders) I see the
100/125/175/175/250 selector,
I think I just found out the real issue, and that information is not
going to help you because it will contain seemingly random indicators
depending on how I size my windows.
VMware Player, like most virtualization software, runs windowed by
default, and that window is dynamically resizeable. Now
Public bug reported:
When opening the Settings, select Displays and then enable "Fractional
Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250%
If you click the first 175% option it will even automatically select the
second one instead.
The third option should likely be 150%
gnome-shell seems to be the right one, filed
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885026
This bug can continue to be about the missing persistence.
** Summary changed:
- Fractional scaling broken in VMware Player
+ Fractional scaling not persisted in VMware Player
--
Public bug reported:
As previously indicated in
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754
When Ubuntu 20.04 is installed in VMware Player 15.5.6, and you change
the display scaling, the mouse becomes "locked" to the window until the
next reboot, as if open-vm-tools is no
I opened https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1885025 for the open-vm-tools issue, I don't know for which
package I should file the bug with the missing 150% setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Related to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but
those report the issues are fixed. They also do not mention the VMware
specific issues.
Install Ubuntu 20.04 in VMware Player,
As a sidenote: the "Fractional scaling selector" in display settings
allows me to choose between 100%, 125%, 175%, 175% and 250%. Note the
duplicate 175% that should likely be 150%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It has been resolved in 1.8.31p1.
https://github.com/sudo-project/sudo/issues/42#issuecomment-599142606
That version hasn't made it into the focal repository yet though.
** Bug watch added: github.com/sudo-project/sudo/issues #42
https://github.com/sudo-project/sudo/issues/42
--
You
Public bug reported:
Two days ago I have reported a bug describing the complete path starting
from the software updater button settings/lifepatch > lifepatch > sign
in/lifepatch Then a window was opened
Line at top: X [] Ubuntu Single Sign-on Account
Next line: same title as above without
I think it's a good idea to set this packages on hold.
aptitude hold unison unison-gtk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875475
Title:
Unison from Ubuntu 20.04 is incompatible with
Public bug reported:
just appeared when i booted my ubuntu 20.04
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mime-support 3.64ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
*** This bug is a duplicate of bug 1842902 ***
https://bugs.launchpad.net/bugs/1842902
Duplicate of #1842902
** This bug has been marked a duplicate of bug 1842902
FFe: create zfs dataset for each user automatically
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1842902 ***
https://bugs.launchpad.net/bugs/1842902
Public bug reported:
When a new user gets created in 20.04 and one uses zfs then the new user
gets a home in /home/newuser but the user does not get his own dataset
but is just placed in /rpool/USERDATA
You can still do power management using any non-gnome power management
tool. Somewhat annoying indeed, but less so than losing my trackpad
every hour ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Had the same issue with my Magic Trackpad. After reading this possibly
related bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113 I decided
to disable upower:
systemctl stop upower
systemctl disable upower
This works around the problem for me.
--
You received this bug
For me it's with Ubuntu18 and Windows 10. It will not install the
bootloader in any of my disks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522661
Title:
grub-efi-amd24-signed failed to install
hope to get it fixst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670410
Title:
package squid 3.5.12-1ubuntu7.3 failed to install/upgrade: subprocess
installed post-installation script returned
: 2.20.9-0ubuntu7.2
AptOrdering:
libgles1:amd64: Install
libglvnd-dev:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Sat Nov 24 22:05:25 2018
DpkgHistoryLog:
Start-Date: 2018-11-24 22:05:24
Commandline: apt-get install -f
Requested-By: niels (1001)
Install: libgles1:amd64
I had the same problem in Ubuntu 18.04.1 with latest Updates to now,
Gnome 3.28.2, 64 Bit System.
Problem:
Preview of ODT-File lets freeze the whole desktop suddenly (suddenly fan begins
to rotate hearable), but nothing works (at least with Ctrl+Alt+F3 I could
switch to console and after login
Attached the output as requested by Daniel van Vugt.
** Attachment added: "Output of journalctl -b-1 > prev_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1799964/+attachment/5205732/+files/prev_boot.txt
--
You received this bug notification because you are a member
Public bug reported:
When I leave my machine for 10 minutes (default is 5) the screen blanks.
Unfortunately it doesn't come back after that, not by hitting a key or moving
the mouse.
I end up stopping the machine and turning it back on again.
May be related with my Vega 64 card/drivers?
Similar to #1799965
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799964
Title:
Ubuntu 18.10 After Blank Screen System Won't Come Back
To manage notifications about this bug go to:
Public bug reported:
Open a zip file with ark
in ark settings choose preview the file with internal previewer.
Open a pdf file from the zip archive.
Save the file using "Save as by choosing a new directory (outside /tmp/)
The file is saved, but when the PDF previewer is closed, the file
buntu)
> Importance: Undecided
> Status: New
>
Side-note: I believe this has been fixed in Artful or Bionic as Ubuntu
has migrated to use the debhelper based dbgsym packages (with only a
minor difference in the filename extension). I remember it as Artful
(but the reference
6085d691aa29c423fa9fa2e240709a
(Should be trivial to cherry-pick).
Thanks,
~Niels
** Bug watch added: Debian Bug tracker #894835
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894835
** Bug watch added: github.com/stsp/dosemu2/issues #597
https://github.com/stsp/dosemu2/issues/597
--
Dan Kegel:
> (Right... that's why I linked to that bug.
Apologies; I just hit reply when I saw the subject. I had not seen you
had already referenced relevant upstream bug. :)
Thanks,
~Niels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Bug watch added: Debian Bug tracker #894895
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894895
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766102
Title:
dh_installchangelogs fails if
bug bionic
>
Hi,
This should have been fixed in debhelper/11.2 as a part of
https://bugs.debian.org/894895.
Thanks,
~Niels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766102
Title:
dh_insta
gradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: debhelper (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: amd64 apport-bug bionic
>
As I recall, this is not because dh_clean does not remove the file but
because dpkg-sou
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/472450
Title:
gnome-keyring crashes for no apparent reason
To manage notifications about this bug go to:
upgrade; and post upgrade. But maybe they only do so for
> systemd native units, and not for init.d->systemd units.
>
>
> ** Also affects: debhelper (Ubuntu)
>Importance: Undecided
>Status: New
>
Hi,
Possibly related to this issue:
https://bugs.debian.org
i have this 3g modem that works but this not show up in top bar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758498
Title:
perl crashed with SIGABRT in _dbus_abort()
To manage notifications
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733453
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745135
Title:
package mysql-server-5.7 5.7.21-0ubuntu0.17.10.1 failed to
install/upgrade: subprocess installed post-installation script
returned
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745135
Title:
package mysql-server-5.7 5.7.21-0ubuntu0.17.10.1 failed to
install/upgrade: subprocess installed post-installation script
returned
Public bug reported:
HP ZBook 15, 2014 model.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
The new version 18.04.3 in bionic-proposed works fine on my other
laptop, too, so I'd call this fixed.
** Changed in: xubuntu-default-settings (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have tested the most recent 18.04.3 version on my work laptop and the
problem appears to have been solved. Haven't tested it on my personal
laptop yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1751414 ***
https://bugs.launchpad.net/bugs/1751414
On Xubuntu, can you try downgrading the package xubuntu-default-settings
from version 18.04.2 to version 18.04.1? Maybe it's related to what I'm
seeing in bug #1752798
(you can find the older package here:
Here's the lightdm.log of the system run with the package version that
prevents booting to Desktop.
Note that it shows that it permanently retries starting lightdm until
the user has had enough and reboots or powers off the system (hence the
section at the end that looks different).
**
For comparision, here's my lightdm.log with the previous package version
where it boots to Desktop successfully.
** Attachment added: "lightdm.log of succeeding run (xubuntu-default-settings
18.04.1)"
Note that on my personal laptop, there's a difference in the Xorg.0.log
regarding the detection of the NVidia gfx board, the failing run using
xubuntu-default-settings package version 18.04.2 and the succeeding run
using version 18.04.1:
$ diff -u <( sed -e 's/^\[[^]]*\] //'
Public bug reported:
Upon upgrading the package from version 18.04.1 to 18.04.2 and
subsequent reboot, the system is rendered unable to start lightdm and
gets stuck in an endless loop retrying.
This happened on 2 laptops, one company machine and one personal
machine.
I'm running bionic beaver
Public bug reported:
The program fails at the first revision with a deleted file.
As described in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204023 there
is a bug in svn-all-fast-export if you use it with svn 1.9 which is the default
at ubuntu 16.04.
There is a new version 1.11
Public bug reported:
Apparently, gitlint needs the Python "sh" package:
$ gitlint --help
Traceback (most recent call last):
File "/usr/bin/gitlint", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3144,
in
Public bug reported:
I ran do-release-upgrade on my server with zesty. But some upgrades were
not performed, it asked me to file a bug:
(Reading database ... 22034 files and directories currently installed.)
Preparing to unpack .../init-system-helpers_1.49ubuntu1_all.deb ...
Unpacking
** Bug watch added: Debian Bug tracker #814856
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814856
** Also affects: debhelper via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814856
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Sorry, misread the bug and unfortunately it seems I cannot undo the fact
that bug is closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675340
Title:
dh_fixperms unsets X permission to node.js
This was fixed in debhelper/10.9 (per https://bugs.debian.org/840913),
which is available in Bionic.
** Bug watch added: Debian Bug tracker #840913
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840913
** Also affects: debhelper via
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707451
Title:
udisksd crashed with SIGSEGV in g_mutex_lock()
To manage notifications about this bug go to:
Public bug reported:
crash in installation
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
CasperVersion: 1.376.2
Date:
The actual warning is from apt and not apt-file. It occurs because
multiple "fetch" directive refer to the same file, but they come from
different lines in the apt sources.list.
As noted (see #1579372), a long term fix would be to provide the
Contents in the "per component" location on the
This looks like it is caused by the Ubuntu specific changes to
dh_installchangelogs.
Namely, the original debhelper will look for (among other) "CHANGES" as
an upstream changelog. Ubuntu have removed this to save disk space and
leads to debhelper picking "changelog" as a candidate for the "main
Hi,
Can you give a case where it would be useful to ask debhelper to build a
package for an architecture, where it is not supported (as declared by
the maintainer)? The only case I can come up with is that the
Architecture field is wrong/out of date. Though in this case, the
proper solution
Please sync apt-file from Debian unstable. The remaining Ubuntu delta
is unnecessary since the downloading of Contents files have been
delegated to APT and configured to look both in the Debian and the
Ubuntu locations.
Thanks,
--
You received this bug notification because you are a member of
ronisation issues will make
it a mess.
Any input on the tools and processes?
Cheers,
Aputsiak Niels Janussen (aj)
Danish translation team
2017-03-16 12:37 GMT+01:00 Gunnar Hjalmarsson <gunna...@ubuntu.com>:
> Hi all,
>
> Today is "DocumentationStringFreeze"[1]. We have f
Danish translations of gnome-sudoku on Launchpad hasn't been updated since
2013.
The upstream translations has been done consistenly, see here:
https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da
Could something be broken?
--
You received this bug notification because you are a member
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672442
Title:
Combined Throttle / Train brake does not work
To manage
Not sure if this is still relevant, but ...
If you are going to make debhelper use ".ddeb" rather than ".deb" for
dbgsym packages (and dpkg doesn't DTRT), I strongly recommend relying on
the "build_and_rename_deb" sub in dh_builddeb rather than computing the
filename yourself. Otherwise,
argh, I meant 3.1.3. Silly me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641283
Title:
Please sync apt-file from Debian unstable
To manage notifications about this bug go to:
Hi Hans,
With my upstream hat on, I believe that delta is redundant thanks to
changes in apt and apt-file. I do not remember the exact apt-file
version that solves it, but I can dig it up if it is relevant (it is
definitely prior to 3.1.4).
Also, I typoed the version; I meant please sync
This is definitely fixed in lintian/2.5.13, where lintian relies on libc
to provide C.UTF-8 rather than generating an en_US.UTF-8.
** Changed in: lintian (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In the mean time, rapt-file has been discontinued as the back end
service has stopped working. I suspect this bug ought to be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263222
Title:
apt-file 3 should support this provided you configure apt to fetch the
Contents files for armhf. Admittedly, this is waiting for #1641283
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296128
Title:
AFAICT, this would fix at least:
* #1296128
* #888316
* #817517
* #767061
* #567895
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641283
Title:
Please sync apt-file from Debian unstable
To
Public bug reported:
Please update the apt-file version in Ubuntu to apt-file/3.1.3.
** Affects: apt-file (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Michael, that is perfectly possible, I have actually adopted it in a
class-file, so I have not tested it with the \makeatletter and
\makeatother commands myself. I tried to (apparently incorrectly) adapt
the code to the use-case of Frédéric. Please try for yourself what
works, thank you for
You can also add the following after \usepackage{titlesec} to only apply
the patch when you're on the specific version of titlesec (which is what
I did on a shared project). Remove the \makeatletter and \makeatother
and change \usepackage to \RequirePackage when you're adding it to your
classfile
Today I received a PDF with forms filled in, that I had to forward as a
normal PDF (using "save as" or print to PDF file). Some fields worked as
expected. But some were missing in the resulting PDF.
After quite some time I tried editing every single form field, ending up
with the same values as
I have a m10 and a k810 and a Ultrathin mouse.
I found out that I can only connect one of the to devices. If some other
(mouse) is connected the logitech keyboard K810 disconects/reconects.
Testet with a dell travell mouse and i get the same k810
disconect/reconect error.
Though I can connect
Public bug reported:
Crashes while being updated
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libavcodec-ffmpeg-extra56:amd64 7:2.7.6-0ubuntu0.15.10.1
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Solved the problem by removing
myisam-recover = BACKUP
and
key_buffer = 16M
from my.cnf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570673
Title:
package
Public bug reported:
crach in update run
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553502
Title:
package linux-image-extra-3.13.0-39-generic 3.13.0-39.66 failed to
install/upgrade: run-parts:
*** This bug is a duplicate of bug 1477617 ***
https://bugs.launchpad.net/bugs/1477617
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553501
Title:
package linux-image-3.13.0-58-generic
*** This bug is a duplicate of bug 1477617 ***
https://bugs.launchpad.net/bugs/1477617
Public bug reported:
problem with upgrade
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-58-generic 3.13.0-58.97
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477617
Title:
linux-image-3.13.0-58-generic 3.13.0-58.97 failed to install/upgrade:
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
*** This bug is a duplicate of bug 1477617 ***
https://bugs.launchpad.net/bugs/1477617
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553501
Title:
package linux-image-3.13.0-58-generic
itwas under upgrade from 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550502
Title:
package systemd 225-1ubuntu9 failed to install/upgrade: subprocess
installed pre-removal script
Public bug reported:
under upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 225-1ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Fri Feb 26 21:01:06 2016
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534647 which may
subsume this bug.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534647/comments/18
verifies ice1712 and mudita(24) work in kernel 4.4.0-6.21
--
You received this bug notification because you are a member of
1 - 100 of 1416 matches
Mail list logo
