apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684485/+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/1592917
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684488/+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/1592917
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684484/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684487/+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/1592917
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684480/+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/1592917
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684479/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684486/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592917
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684483/+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/1592917
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684482/+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/1592917
apport information
** Tags added: apport-collected xenial
** Description changed:
On an up-to-date 14.04.x, I started do-release-upgrade -d to upgrade to
ubuntu 16.04.
At about 50% of the installation of packages, do-release-upgrade stucks
in the following manner:
- cpu runs at
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684481/+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/1592917
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684478/+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/1592917
Title:
After trying to stop or teardown apparmor, I still get
aa-status
apparmor module is loaded.
3 profiles are loaded.
3 profiles are in enforce mode.
/usr/lib/cups/backend/cups-pdf
/usr/sbin/cupsd
/usr/sbin/cupsd//third_party
0 profiles are in complain mode.
0 processes have profiles
Still in the middle of the (stucked) upgrade, I get:
apport-collect 1592917
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository
related: #1370930
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592917
Title:
do-release-upgrade stuck when dealing with apparmor profile for cupsd
To manage notifications about this bug go to:
output of ps aux | grep dpkg is attached.
Note that there is a process with no progress (stucks)
root 20108 0.0 0.0 4508 1624 pts/18 S+ 18:42 0:00 /bin/sh
/var/lib/dpkg/info/cups-daemon.postinst configure 1.7.2-0ubuntu1.7
** Attachment added: "output of ps aux | grep dpkg"
In syslog, I get a lot of complaints from apparmor:
Jun 15 19:06:02 lat61 kernel: [10041.854940] audit: type=1400
audit(1466010362.719:539): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=24942
comm="apparmor_parser"
Jun 15 19:06:02
do-release-upgrade stucks at this place:
plymouth (0.9.2-3ubuntu13.1) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
update-rc.d: warning: start and stop actions are no
Public bug reported:
On an up-to-date 14.04.x, I started do-release-upgrade -d to upgrade to
ubuntu 16.04.
At about 50% of the installation of packages, do-release-upgrade stucks
in the following manner:
- cpu runs at 0%~ and there is no disk I/O for about 15 minutes now
- do-release-upgrade
Generally, the frozen desktop was very very rare/seldom. I'd have to
work weeks with the cdimage to reproduce this issue.
In the meantime I don't experience frozen desktops in Ubuntu 14.04.4 any
more. Maybe it's already fixed even in 14.04.4. Maybe I see it again in
a month or so.
For the
@penalvch no, /var/crash is empty:
/var/crash$ ls -la
insgesamt 0
drwxrwsrwt 1 root whoopsie 0 Jun 1 10:10 .
drwxr-xr-x 1 root root 130 Jul 26 2015 ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674843/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551566
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674846/+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/1551566
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674841/+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/1551566
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674842/+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/1551566
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674845/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551566
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674844/+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/1551566
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674833/+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/1551566
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674836/+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/1551566
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674840/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
My desktop just froze and I could not press any keys.
When I tried CTRL+ALT+F1 I got logged out from my gnome session and the
graphical (!) login window appeared.
There's some messages in my syslog, e.g.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674839/+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/1551566
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674834/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674838/+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/1551566
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674837/+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/1551566
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674835/+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/1551566
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674832/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551566
With Ubuntu 14.04, Kernel 3.16 (from HES), I could btrfs-balance a non-
raid /dev/sda2 btrfs fs with
cd /mnt
mkdir fulldisk
mount /dev/sda2 fulldisk
btrfs device add /dev/sdb fulldisk
btrfs balance start fulldisk
btrfs device delete /dev/sdb fulldisk
But with Ubuntu 14.04, Kernel
As described in my previous comment, the fs was available in read-write
mode again.
I added another disk to the btrfs and with the additional space I was
able to rerun and successfully finish the btrfs balance operation (as
described in https://www.slicewise.net/debian/balancierung-eines-vollen-
I rebooted the system in the meantime. It now had Kernel 4.2.0-30.36
from previous updates:
cat /proc/version_signature
Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
During the reboot, the system performed some disk I/O for several hours.
Before services like sshd became available. I guess this
@jsalisbury
What exactly should I test on a broken file system with a newer Kernel?
How could this help you? If btrfs balance corrupted my file system, how
should a newer kernel fix that?
If you can tell me test a scenario which will help you to see if the bug
is fixed upstream, I'd be happy to
Checking the underlying mdraid with
echo check > /sys/block/md0/md/sync_action
now has finished and it is just fine:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks super 1.2
Now, this one is funny after ~2 days:
# btrfs balance status x
Balance on 'x' is running
0 out of about 2797 chunks balanced (533 considered), 100% left
# btrfs balance cancel x
ERROR: balance cancel on 'x' failed - Read-only file system
So the balance is still running, consuming 100% of one
cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=8157548k,nr_inodes=2039387,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs
I found a few entries in kern.log, nothing special during btrfs balance:
Mar 19 03:47:03 server kernel: [2970569.341605] BTRFS info (device dm-0):
relocating block group 9553211031552 flags 36
Mar 19 04:01:08 server kernel: [2971415.588391] BTRFS info (device dm-0):
relocating block group
Error messages in dmesg |tail are still ongoing, presumably originating
from the btrfs command which still is eating 100% of the cpu,
I did not reboot yet nor kill the btrfs process (pid 27516).
Here's two lines from two of the latest error messages in dmesg:
[3111643.576434] []
Something noticable: The command btrfs is consuming 100% of the cpu for
a long time:
# top
[...]
PID BENUTZER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
27516 root 20 0 15476132 0 R 100,0 0,0 1348:33 btrfs
I assume that this process originates from my
Currently, I'm checking the md-raid (raid 1) with
echo check > /sys/block/md0/md/sync_action
I have 2 x 3.5TB hard drives, so this will take some while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The underlying md-raid (mirroring) is fine. So according to md-raid
status, there's nothing wrong with the mirrored partitions:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks
Some relevant lines from /var/log/syslog:
Mar 19 19:15:10 server smartd[2251]: Device: /dev/sdb [SAT], SMART Usage
Attribute: 194 Temperature_Celsius changed from 107 to 106
Mar 19 07:59:21 server console-kit-daemon[2041]: GLib-CRITICAL: Source ID 376
was not found when attempting to remove it
related: https://www.mail-archive.com/linux-
bt...@vger.kernel.org/msg48609.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage
I have # btrfs --version
Btrfs v3.12
Kernel is from Hardware enablement stack 14.04.4, Btrfs-tools from
ubuntu's package respectively.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
# apt-cache policy btrfs-tools
btrfs-tools:
Installiert: 3.12-1ubuntu0.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage
Related: https://www.spinics.net/lists/linux-btrfs/msg48037.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage notifications about this
Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage notifications about
For my setup, btrfs file system runs on top of a LUKS encrypted
partition which itself is on top of a mdraid (mirroring).
The Layout is:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 2,7T 0 disk
├─sda1 8:10
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559723/+attachment/4605660/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559723/+attachment/4605659/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Public bug reported:
I performed a btrfs balance for a disk which ran out of space. When I
did this some months ago, I got an error message, but this time, I got a
soft lockup and the file system got mounted read-only:
# cat /proc/version_signature
Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
Note that some months ago (when I got the error message), I still was
able to cleanly free up some diskspace and perform a clean btrfs balance
(which freed a lot of space).
My hope was that I'd get an error message and exit cleanly if disk space
is missing. Instead, I got the soft lockup.
--
related: #1349711
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559723
Title:
soft lockup during btrfs balance
To manage notifications about this bug go to:
This ppa solved it for me:
https://launchpad.net/~mpanella/+archive/ubuntu/virt-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496357
Title:
XML error: ram attribute only supported for
Bug still exists in 14.04 (up-to-date)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496357
Title:
XML error: ram attribute only supported for type of qxl
To manage notifications about this bug
Public bug reported:
My desktop just froze and I could not press any keys.
When I tried CTRL+ALT+F1 I got logged out from my gnome session and the
graphical (!) login window appeared.
There's some messages in my syslog, e.g. gdk-warning gnome-session fatal
io error 11 (resource temporarily
For copy-pasteable add-apt-repository commands on the website I filed a
new issue for launchpad itself:
https://bugs.launchpad.net/launchpad/+bug/1547343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Covered by this issue, https://wiki.ubuntuusers.de/some/program has
become available in the meantime and it's https-only which is good.
To go for
add-apt-repository ppa:
is a nice way and I'm aware of this. Nice as long as key material is
transferred in a secure manner (e.g. https-only).
But
@daniel-serpell I fully agree. This should also made available for HES
wily.
Execution of
sudo apt-get install --install-recommends linux-generic-lts-wily
proposes to install linux-lts-wily-tools, but this package is not
available in the repo and the additional package is not installed
Tried to reproduce this issue with a clean install of ubuntu 14.04:
- Installed ubuntu desktop 14.04.1 from original media (in KVM machine)
- update (via apt-get update && apt-get upgrade && apt-get dist-upgrade
- reboot
- install same printer (as used in all previous attemps: Kyocera FS-1020d)
-
Same applies for ubuntu 15.10 using LO 5.0.3.2 build
1:5.0.3~rc2-0ubuntu1:
Cannot reproduce this issue with ubuntu 15.10 and LO 5.0.3.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534927
Title:
I further tracked it down to see why the system which has the problem
differs from the behaviour of a fresh install.
And I found the difference: I had a third party LO extension installed:
LibreOffice E-Porto 1.0.3 from https://www.deutschepost.de/de/i
Tried to reproduce this issue with a fresh install of ubuntu 15.10 (in
KVM):
- Performed all updates available via apt-get (this is pretty much the only
thing I was doing)
- Libreoffice version is 5.0.2.2, build-id 00m0 (from repository)
Result: Cannot reproduce this issue in ubuntu 15.10. I
Public bug reported:
How to reproduce:
- open testcase.odt writer document
- open testcase.odt calc document
- Press STRG+P in calc
=> Result: Writer document is shown in printing preview
- Press OK
=> Result:
===> Using 1:5.0.3~rc2-0ubuntu1~trusty2 from ppa, the writer document is printed
===>
The problem can be worked around by not opening testcase.odt. However,
if the user accidently does not apply this workaround, he or she is
faced with the problem as soon as he or she presses STRG+P (or uses the
printing dialog from the menu).
As already mentioned, I was faced with data loss in
This is a screenshot taken from 1:5.0.3~rc2-0ubuntu1~trusty2. What you
can see is that when printing in calc, the text from writer is shown in
the preview while being different from the document in calc.
This is pretty much the same in 1:4.2.8-0ubuntu3.
The behaviour is reproducable, meaning it
I further tracked it down to see why the system which has the problem
differs from the behaviour of a fresh install.
And I found the difference: I had a third party LO extension installed:
LibreOffice E-Porto 1.0.3 from https://www.deutschepost.de/de/i
** Bug watch added: Document Foundation Bugzilla #97182
https://bugs.documentfoundation.org/show_bug.cgi?id=97182
** Also affects: df-libreoffice via
https://bugs.documentfoundation.org/show_bug.cgi?id=97182
Importance: Unknown
Status: Unknown
--
You received this bug
There's some documentation about how to check the hash with gpg and
which key is authorized at
https://help.ubuntu.com/community/VerifyIsoHowto . This page is linked
in https://help.ubuntu.com/community/UbuntuHashes . So finally, there is
a statement available which key should be valid. Plus, this
*** This bug is a security vulnerability ***
Public security bug reported:
ubuntu offers an overview to get hashes of download files at
https://help.ubuntu.com/community/UbuntuHashes (via HTTPS).
It then takes me to http://releases.ubuntu.com (via HTTP). Which then
takes me to e.g.
I assume the upstream bugfix was https://github.com/virt-manager/virt-
manager/commit/51e5a471202a67e3c9c1dd53c0afc333d77933c9 which was fixed
for 1.2.0. Could this be backported, please?
** Bug watch added: Red Hat Bugzilla #1169295
https://bugzilla.redhat.com/show_bug.cgi?id=1169295
** Also
Same bug was resolved in Redhat 7.0 according to
https://bugzilla.redhat.com/show_bug.cgi?id=920549
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496357
Title:
XML error: ram attribute only
Public bug reported:
Reproduce with:
- Configure a VM with spice display and QXL video device, store and eventually
run the machine
- Configure back to VNC display and video device other than QXL (e. g. Cirrus
model)
- => error appears.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package:
That fix was for https://bugzilla.redhat.com/show_bug.cgi?id=1169295
which was fixed in Redhat 7.1
https://bugzilla.redhat.com/show_bug.cgi?id=920549 is a duplicate of
https://bugzilla.redhat.com/show_bug.cgi?id=928882 according to
Use case/Motivation:
Sometimes I boot an existing machine with an ISO-CD like e.g.
SystemRescueCD to perform some maintenance tasks (e.g. extend
partitions). SystemRescueCD, however, cannot start its x-server in Spice
mode ("no screens found").
--
You received this bug notification because you
I reported upstream bug report
https://bugzilla.mozilla.org/show_bug.cgi?id=1204551
** Bug watch added: Mozilla Bugzilla #1204551
https://bugzilla.mozilla.org/show_bug.cgi?id=1204551
** Also affects: cups via
https://bugzilla.mozilla.org/show_bug.cgi?id=1204551
Importance: Unknown
There's a cups bug report which was closed unresolved:
https://www.cups.org/str.php?L3950+P-1+S0+C0+I0+E0+Qfirefox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802942
Title:
printing PDFs (and
Maybe related:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/369503
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802942
Title:
printing PDFs (and other complex documents) from GTK
The guys at cups do not feel responsible for linux issues as documented
in https://www.cups.org/str.php?L4715
In the meantime I further tracked it down:
- Played around with printer drivers, using Kyocera's PPD, the PPD provided by
ubuntu and also gave PPD from
I've sent the pdf files to http://pdf-analyser.edpsciences.org to see
what the difference is.
All samples provide the same set of fonts.
But there is a difference between the non-working samples and working samples:
non-working test2.pdf and print-to-file.pdf are reported to be created by cairo
Cairo 1.9.5 dates back to ~2009/2010 according to
http://cairographics.org/news/.
. My ubuntu 14.04.3 came shipped with libcairo2 package version
1.13.0~20140204-0ubuntu1.1 which dates back to ~2013/2014 according to
http://cairographics.org/news/.
I guess that Firefox 40.0.3 still comes shipped
I guess that Cairo is part of the Gecko engine which then is used by
firefox and thunderbird.
My Firefox 40.0.3 comes shipped with Gecko/20100101 according to
about:support tab:
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101
Firefox/40.0
which basically explains why cairo is so
When I choose the "print to file" in the printing dialog in firefox, I
get a pdf print-to-file.pdf created by firefox.
I have the same problem when I try print this file with cat print-to-
file.pdf |lpr -P fs-1020d -# 1
/var/spool/cups then contains a file which I renamed to pdf print-to-
** Also affects: cups-filters (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/802942
Title:
printing PDFs (and other complex documents) from GTK
The only workaround I'm aware of is to use the "print to file" dialog
and then print the corresponding print-to-file.pdf with evince.
When I print the file with evince, I can find a file in /var/spool/cups
which I renamed to print-to-file-cups-from-evince.pdf. Note that this
file is 15% smaller
As far as I can see, gecko ubstream uses cairo 1.9.5 from 2010-01-21
which they are patching over and over.
https://github.com/mozilla/gecko-dev/blob/master/gfx/cairo/README
http://cgit.freedesktop.org/cairo/commit/?id=12d521df8acc483b2daa844d4f05dc2fe2765ba6
(where they forked at 2010-01-21)
There should also be an add-apt-repository statement for each repo
documentation.
E. g. for
https://launchpad.net/~docker-maint/+archive/ubuntu/testing
there should be an _additional_ line
sudo add-apt-repository ppa:docker-maint/testing
which the user can can copy-paste.
Reason:
- This is ways
For me, simulation works when I use libegl1-mesa-lts-vivid instead of
libegl1-mesa-drivers-lts-vivid. libegl1-mesa-drivers-lts-utopic is
removed by this.
sudo apt-get -s install --install-recommends linux-generic-lts-vivid
xserver-xorg-lts-vivid libgl1-mesa-glx-lts-vivid libegl1-mesa-lts-vivid
I was also missing the Button “New Hardware Support is Available” in the
update messenger. I assume this was because libegl1-mesa-drivers-lts-
vivid was missing.
If you add a meta package with dependency to libegl1-mesa-lts-vivid the
dependencies can be resolved and the button might appear.
--
Replacing libegl1-mesa-drivers-lts-vivid with libegl1-mesa-lts-vivid
instead worked for me:
sudo apt-get install --install-recommends linux-generic-lts-vivid
xserver-xorg-lts-vivid libgl1-mesa-glx-lts-vivid libegl1-mesa-lts-vivid
after execution and reboot:
uname -a
Linux lat61
https://wiki.ubuntuusers.de/LTS_Enablement_Stacks describes another way
to install the 14.04.3 HES which also does not work:
sudo apt-get -s install --install-recommends linux-generic-lts-vivid
xserver-xorg-core-lts-vivid xserver-xorg-lts-vivid
xserver-xorg-video-all-lts-vivid
Same for me when I replace utopic with vivid (I tracked apt usage of
older installs of HESes on http://www.slicewise.net/debian/hardware-
enablement-stack-fuer-ubuntu-1404-lts-trusty-tahr/):
sudo apt-get -s install --install-recommends linux-generic-lts-vivid
xserver-xorg-lts-vivid
301 - 400 of 452 matches
Mail list logo
