[Desktop-packages] [Bug 819995] Re: "Print to file" PDF metadata broken
I have tried some solutions before i found this bug, An extract of metadata made with exiftool (libimage-exiftool-perl 9.46-1) shows an important difference on a document that displaying dates right, and one sample print-to-file, the tags for PDF related date info is totally missing: -PDF:CreateDate= -PDF:ModifyDate= Example command: exiftool -args -G1 --filename --directory PDF_FILE_NAME.PDF Example output of Print-to-File: -ExifTool:ExifToolVersion=9.46 -System:FileSize=107 kB -System:FileModifyDate=2018:02:22 00:56:18+01:00 -System:FileAccessDate=2018:02:22 00:56:40+01:00 -System:FileInodeChangeDate=2018:02:22 01:30:18+01:00 -System:FilePermissions=rw-rw-r-- -File:FileType=PDF -File:MIMEType=application/pdf -PDF:PDFVersion=1.5 -PDF:Linearized=No -PDF:PageCount=1 -PDF:Creator=cairo 1.13.1 (http://cairographics.org) -PDF:Producer=cairo 1.13.1 (http://cairographics.org) Example output of PDF with working dates: -ExifTool:ExifToolVersion=9.46 -System:FileSize=3.2 MB -System:FileModifyDate=2015:11:02 14:37:59+01:00 -System:FileAccessDate=2018:02:22 01:49:42+01:00 -System:FileInodeChangeDate=2015:11:02 14:37:59+01:00 -System:FilePermissions=rw-r- -File:FileType=PDF -File:MIMEType=application/pdf -PDF:PDFVersion=1.5 -PDF:Linearized=No -PDF:PageCount=89 -PDF:Language=en-US -PDF:TaggedPDF=Yes -PDF:Title=XenServer 6.x Best Practices -PDF:Author=Daily, Camille -PDF:Keywords=Minimum Restrictions, No Restrictions -PDF:Creator=Microsoft® Word 2013 -PDF:CreateDate=2013:10:30 08:44:27-05:00 -PDF:ModifyDate=2013:10:30 08:44:27-05:00 -PDF:Producer=Microsoft® Word 2013 evince 3.10.3-0ubuntu10.4 amd64 libcairo2 1.13.0~20140204-0ubuntu1.1 amd64 Description:Ubuntu 14.04.5 LTS Kernel: Linux 3.13.0-142-generic #191-Ubuntu SMP x86_64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/819995 Title: "Print to file" PDF metadata broken Status in cairo package in Ubuntu: Confirmed Bug description: Ubuntu 11.04 Natty Narwhal 64bit libgnomeprint2.2-0 - 2.18.8-0ubuntu1 It seems libgnomeprint sends wrong date, Jan 1st 1970 to PDF metadata when printing to file (PDF) This behaviour is reproducible for me on both 64bit and 32bit versions of 11.04 Using dialog "print to file" choosing PDF as output format "Creation Date" and "Last edited" is always set to "Thu 01 Jän 1970 00:59:59 CET" which is afaik Date 0 for Unices. I am using german localization but in case of needed screenshots I can of course change to english. This behaviour happens on my main machine (64bit) and my old notebook (32bit) looking to my self produced PDFs from 10.10 definitely show the same behaviour, I could also look on old backups for even older version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/819995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182007] Re: Failed to SUID root
forgot to paste this lint to the changelog https://launchpad.net/ubuntu/+source/signon/8.57+15.10.20150616-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1182007 Title: Failed to SUID root Status in signon package in Ubuntu: Confirmed Bug description: signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available. This report appears in syslog each time Empathy tries and fails to connect to Google Talk using the google-talkplugin interface. It is not clear whether this SUID report is related to the Empathy failure. See bug #1168582 "Google talk "Requires Authorization" after suspend/resume" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1182007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182007] Re: Failed to SUID root
According to a gitlab Commit 18381573 authored 2 years ago by Alberto Mardegan: https://gitlab.com/accounts-sso/signond/commit/18381573beaa4efe5b115ccdf3b3a689e98a72c6 signond: remove warning about not being root Usually signond doesn't run as root; if necessary, this warning can be moved to an extension. This change made it into signon 8.57+15.10.20150616-0ubuntu1 so it should be fixed in wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1182007 Title: Failed to SUID root Status in signon package in Ubuntu: Confirmed Bug description: signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available. This report appears in syslog each time Empathy tries and fails to connect to Google Talk using the google-talkplugin interface. It is not clear whether this SUID report is related to the Empathy failure. See bug #1168582 "Google talk "Requires Authorization" after suspend/resume" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1182007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
I know rather old thing, but this got irritating me now. one bit of info: This shows that plymouth-ready is after lightdm... /var/lib/plymouth/boot-duration 0.978:avahi-daemon 0.979:statd 0.979:udev-finish 0.993:rc-sysinit 0.993:rc 0.993:tty4 0.993:tty5 0.993:acpid 0.993:anacron 0.993:tty2 0.993:tty3 0.993:dmesg 0.993:tty6 0.993:plymouth-stop 0.993:cron 0.993:atd 0.993:irqbalance 0.993:whoopsie 0.993:libvirt-bin 0.994:apport 0.995:qemu-kvm 0.998:lightdm 0.999:plymouth-ready -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in gdm package in Ubuntu: Fix Released Status in kde-workspace package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in xorg-server-lts-quantal package in Ubuntu: Invalid Status in gdm source package in Precise: Fix Released Status in kde-workspace source package in Precise: Confirmed Status in lightdm source package in Precise: Fix Released Status in plymouth source package in Precise: Fix Released Status in xorg-server-lts-quantal source package in Precise: Triaged Status in gdm source package in Raring: Fix Released Status in kde-workspace source package in Raring: Won't Fix Status in lightdm source package in Raring: Fix Released Status in plymouth source package in Raring: Fix Released Status in xorg-server-lts-quantal source package in Raring: Invalid Status in gdm source package in Saucy: Fix Released Status in kde-workspace source package in Saucy: Won't Fix Status in lightdm source package in Saucy: Fix Released Status in plymouth source package in Saucy: Fix Released Status in xorg-server-lts-quantal source package in Saucy: Invalid Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 998001] Re: Have to confirm certificate on every connection
Dont know if that would help, but a small how to import the self signed Windows Server CA cert to trusted CA list would solve this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/998001 Title: Have to confirm certificate on every connection Status in “remmina” package in Ubuntu: Confirmed Bug description: Every time I connect to a server it asks me to confirm the fingerprint of the certificate is correct. Whilst being quite useless as humans generally can't read hexadecimal very well, I suppose I could cross reference it the first time I connect. The fingerprint should be saved and the user should not be bothered on repeat connections. This is a security issue because it is impractical for the user to check the fingerprint every time they connect, especially considering how easy it would be for Remmina to cache. This dialog will simply be ignored and encourage the user to blindly accept every dialog they see, defeating the point of it to begin with. Ubuntu 12.04 32-bit / 0.9.99.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/998001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 943880] Re: Xorg crashed with SIGABRT in __libc_message() from malloc_printerr() via XIDestroyDeviceProperty
I was curious about the dialog i receive often about some internal error
after startup, or while using the system, and looked at the details.
After that i found this bug.
The fact that in the last comments the touchpad is mentioned, and the
base report is loenovo x220 related, I can only provide a litte bit as
addition:
Current system with the latest updates:
Linux x220i 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
The synaptics package is:
xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise2
The syndaemon is running with params:
syndaemon -i 2.0 -K -R -t
And the most important info, i have totally disabled my touchpad for 5
months at least , because i am full satisfied with the trackpoint since
i used it with IBM thinkpads for decades. So the touchpad is disabled at
boot every time.
Do i need the syndaemon if i never want to use the touchpad? That would
be at least for only me(!) a possible workaround.
I also think the crash notification comes more frequently after i use an
external monitor and disconnect it (before or after shutdown does not
matter), and boot next time without the external monitor.
I hope this helps.
--
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/943880
Title:
Xorg crashed with SIGABRT in __libc_message() from malloc_printerr()
via XIDestroyDeviceProperty
Status in “xorg-server” package in Ubuntu:
Confirmed
Status in “xorg-server” source package in Precise:
Confirmed
Bug description:
#2 0xb71de835 in __GI_abort () at abort.c:91
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x407, sa_sigaction =
0x407}, sa_mask = {__val = {3075852732, 3075864776, 6, 8, 3217292836,
3072910926, 0, 0, 3072250189, 3073691636, 3073691636, 11, 3217294372,
3073032746, 2, 3217292836, 8, 0, 3217295596, 0, 7, 0, 5, 3217292940,
3217292932, 8, 3073420904, 3073420908, 3075850240, 2, 3076003257, 3}}, sa_flags
= 4, sa_restorer = 0xb730893f}
sigs = {__val = {32, 0 repeats 31 times}}
#3 0xb7214f9a in __libc_message (do_abort=2, fmt=0xb730cf3c *** glibc
detected *** %s: %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
ap = 0xb6eee000
ap_copy = 0xb6eee000
fd = 2
on_2 = optimized out
list = optimized out
nlist = optimized out
cp = optimized out
written = optimized out
#4 0xb721fae2 in malloc_printerr (action=optimized out, str=optimized
out, ptr=0xb98da700) at malloc.c:5007
buf = b98da700
cp = optimized out
#5 0xb767bd1b in XIDestroyDeviceProperty (prop=0xb98da700) at
../../Xi/xiproperty.c:631
No locals.
#6 0xb767c2a4 in XIDeleteAllDeviceProperties (device=0xb98d7c18) at
../../Xi/xiproperty.c:648
prop = 0xb98da700
next = 0xb98d8360
curr_handler = optimized out
next_handler = optimized out
#7 0xb7587b2d in CloseDevice (dev=0xb98d7c18) at ../../dix/devices.c:919
screen = 0xb947d6d0
classes = optimized out
j = optimized out
#8 0xb758c0dd in RemoveDevice (dev=0xb98d7c18, sendevent=1 '\001') at
../../dix/devices.c:1117
prev = optimized out
tmp = 0xb98d7c18
next = 0xb98cbe18
ret = optimized out
screen = optimized out
deviceid = 11
initialized = 1
flags = {0 repeats 11 times, 8, 0 repeats 28 times}
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
.tmp.unity.support.test.0:
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Wed Feb 29 14:49:40 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: No
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:21da]
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386
(20120201.1)
MachineType: LENOVO 4287CTO
ProcCmdline: /usr/bin/X :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8
-novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic-pae
root=UUID=4df4306d-0fbd-4fb5-bbda-ee15a859a65d ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
raise () from /lib/i386-linux-gnu/libc.so.6
abort () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
?? ()
Title: Xorg crashed with SIGABRT in raise()
