Same thing for me. Worked on 24.04. Often does not work on 24.10. I
am using X11 as well, I have not seen it when I use Wayland.
Here's part of my crash report:
SegvAnalysis:
Segfault happened at: 0x5c4558ac1515 : mov
(%rbx),%rdi
Stacktrace:
#0 0x5c4558ac1515 in NAUTILUS_VIEW_GET_I
Same thing for me. Worked on 24.04. Often does not work on 24.10. I
am using X11 as well, I have not seen it when I use Wayland.
Here's part of my crash report:
SegvAnalysis:
Segfault happened at: 0x5c4558ac1515 : mov
(%rbx),%rdi
Stacktrace:
#0 0x5c4558ac1515 in NAUTILUS_VIEW_GET_I
Same thing for me. Worked on 24.04. Often does not work on 24.10. I
am using X11 as well, I have not seen it when I use Wayland.
Here's part of my crash report:
SegvAnalysis:
Segfault happened at: 0x5c4558ac1515 : mov
(%rbx),%rdi
Stacktrace:
#0 0x5c4558ac1515 in NAUTILUS_VIEW_GET_I
So, I have been getting hit with this every day or so on my rather old
HP Pavilion desktop. I thought I might be getting hit with this problem
because the desktop was a few years old.
But now I just got hit with it on a new Dell Inspiron laptop which I
bought this year. Same error in my kern.log
So, I have been getting hit with this every day or so on my rather old
HP Pavilion desktop. I thought I might be getting hit with this problem
because the desktop was a few years old.
But now I just got hit with it on a new Dell Inspiron laptop which I
bought this year. Same error in my kern.log
I was hitting the bug with "4.10.0-19-generic #21-Ubuntu". With a
standard apt-get update and upgrade (no special kernel install) I am now
on "4.10.0-20-generic #22-Ubuntu".
Got hit with the same bug on this new kernel. So the most recent
general kernel update did not fix anything for me. Incid
I was hitting the bug with "4.10.0-19-generic #21-Ubuntu". With a
standard apt-get update and upgrade (no special kernel install) I am now
on "4.10.0-20-generic #22-Ubuntu".
Got hit with the same bug on this new kernel. So the most recent
general kernel update did not fix anything for me. Incid
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
The top of the stacktrace is the same as bug #1674838.
** This bug has been marked a duplicate of bug 1674838
kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
--
You received
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
The top of the stacktrace is the same as bug #1674838.
** This bug has been marked a duplicate of bug 1674838
kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
--
You received
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
"It claims that there is a kernel bug on line 129 of linux/swapops.h
which seems to indicate that it is trying to migrate an unlocked page
for some reason."
This is a duplicate of bug #1674838, diagnosis is
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
"It claims that there is a kernel bug on line 129 of linux/swapops.h
which seems to indicate that it is trying to migrate an unlocked page
for some reason."
This is a duplicate of bug #1674838, diagnosis is
I upgraded from 16.10 to 17.04 three days ago. I have been hit with
this three times in three days. I am using my desktop, and then
everything freezes.
This last time I had a little more freedom. I was using firefox when it
became unresponsive. I opened up a terminal and ran "ps axu" and it
hu
I upgraded from 16.10 to 17.04 three days ago. I have been hit with
this three times in three days. I am using my desktop, and then
everything freezes.
This last time I had a little more freedom. I was using firefox when it
became unresponsive. I opened up a terminal and ran "ps axu" and it
hu
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
** This bug has been marked a duplicate of bug 1674838
kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
** This bug has been marked a duplicate of bug 1674838
kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
Public bug reported:
I upgraded from 16.10 to 17.04 three days ago. Three times since then,
I have had a kernel bug, which froze my desktop.
Each times it has happened while I was using firefox.
This tim
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
Public bug reported:
I upgraded from 16.10 to 17.04 three days ago. Three times since then,
I have had a kernel bug, which froze my desktop.
Each times it has happened while I was using firefox.
This tim
I get a segmentation fault as well. I have OPENARENA_BACKTRACE set to 1
in my shell environment. What I get is:
Thread 1 "ioquake3" received signal SIGSEGV, Segmentation fault.
BotFreeInfoEntities () at code/botlib/be_ai_goal.c:458
458 code/botlib/be_ai_goal.c: No such file or directory.
[..
I get a segmentation fault as well. I have OPENARENA_BACKTRACE set to 1
in my shell environment. What I get is:
Thread 1 "ioquake3" received signal SIGSEGV, Segmentation fault.
BotFreeInfoEntities () at code/botlib/be_ai_goal.c:458
458 code/botlib/be_ai_goal.c: No such file or directory.
[..
Going on skomorokh's advice I downloaded the apparmor tools to put
things into complain mode and so forth.
Theoretically this should not have fixed firefox, but it seems to have
done so for me. Firefox always used to freeze within minutes for me.
Now it hasn't frozen in days. I didn't do anythi
Going on skomorokh's advice I downloaded the apparmor tools to put
things into complain mode and so forth.
Theoretically this should not have fixed firefox, but it seems to have
done so for me. Firefox always used to freeze within minutes for me.
Now it hasn't frozen in days. I didn't do anythi
Attached is a gdb trace of when the error happens. Here is a snippit
of it:
11 0x7fb2a6df8e88 in clutter_parse_args (error=0x7ffc8f85b1d8, argv=0x0,
argc=0x0) at clutter-main.c:1770
#12 clutter_init (argc=0x0, argv=0x0) at clutter-main.c:1832
#13 0x7fb2a70c3724 in ?? ()
from /usr
Attached is a gdb trace of when the error happens. Here is a snippit
of it:
11 0x7fb2a6df8e88 in clutter_parse_args (error=0x7ffc8f85b1d8, argv=0x0,
argc=0x0) at clutter-main.c:1770
#12 clutter_init (argc=0x0, argv=0x0) at clutter-main.c:1832
#13 0x7fb2a70c3724 in ?? ()
from /usr
Oops, icedove is a branded thunderbird, not firefox. They seem to share
some functions though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1521789
Title:
firefox freezes with GStr
Oops, icedove is a branded thunderbird, not firefox. They seem to share
some functions though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521789
Title:
firefox freezes with GStreamer-WARNING **
Also note https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803386 :
Oct 29 09:52:56 boohn icedove.desktop[2410]: #007[NPAPI 6706] ###!!! ABORT:
Aborting on channel error.: file
/build/icedove-RFEbAP/icedove-42.0~b1/mozilla/ipc/glue/MessageChannel.cpp, line
1768
Oct 29 09:52:56 boohn icedove.de
Also note https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803386 :
Oct 29 09:52:56 boohn icedove.desktop[2410]: #007[NPAPI 6706] ###!!! ABORT:
Aborting on channel error.: file
/build/icedove-RFEbAP/icedove-42.0~b1/mozilla/ipc/glue/MessageChannel.cpp, line
1768
Oct 29 09:52:56 boohn icedove.de
This is a screenshot of what happens. Errors are spit out on the
command line which launched firefox, and then the application becomes
grey.
** Attachment added: "Grey frozen Firefox"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1521789/+attachment/4528333/+files/Screenshot%20from%2
This is a screenshot of what happens. Errors are spit out on the
command line which launched firefox, and then the application becomes
grey.
** Attachment added: "Grey frozen Firefox"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1521789/+attachment/4528333/+files/Screenshot%20from%2
I just upgraded to 15.10. I created a new account to replicate the bug,
so no old settings would interfere.
I launch firefox, go through some tabs, and within a few minutes it
freezes. This happens over and over when I try to use firefox. This
did not happen on 15.04. But when I upgraded to 15
Public bug reported:
firefox freezes
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: firefox 42.0+build2-0ubuntu0.15.10.1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.19.1-0ubuntu5
Architecture:
Public bug reported:
firefox freezes
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: firefox 42.0+build2-0ubuntu0.15.10.1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.19.1-0ubuntu5
Architecture:
I just upgraded to 15.10. I created a new account to replicate the bug,
so no old settings would interfere.
I launch firefox, go through some tabs, and within a few minutes it
freezes. This happens over and over when I try to use firefox. This
did not happen on 15.04. But when I upgraded to 15
Public bug reported:
I upgraded to Ubuntu 14.04 (Trusty Tahir).
As the screenshot attached shows, chart customization in Gnumeric has
broken somewhat. In 13.10, I would click on a chart, go to customize,
and then the options would be shown. If you see the screenshot, the very
vertically small "S
"you did not follow the instructions verbatim"
I did follow the instructions verbatim for how you want bugs reported.
It would have been reported that way to begin with if it had worked to
begin with (prior to your comment). Unless you have x-ray vision, you
would have no way of knowing what inst
** Bug watch added: GNOME Bug Tracker #721598
https://bugzilla.gnome.org/show_bug.cgi?id=721598
** Also affects: gnumeric via
https://bugzilla.gnome.org/show_bug.cgi?id=721598
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ub
If you read the comment above yours, it says that that method does not
allow for bug reports.
** Changed in: gnumeric (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Regarding the method said to report bugs - that method will not let me
report bugs. It says Show Details, Leave Closed or Relaunch. Choosing
any of those methods leads to no way to report a bug.
** Changed in: gnumeric (Ubuntu)
Status: Invalid => New
--
You received this bug notificatio
** Attachment added: "_usr_bin_gnumeric.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/1266268/+attachment/3941361/+files/_usr_bin_gnumeric.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Description changed:
- I upgraded from Ubuntu 12.04 to 12.10. Gnumeric now does not open
- certain gnumeric spreadsheets which it did previously on 12.04.
+ I upgraded from Ubuntu 13.04 to 13.10. Gnumeric now does not open
+ certain gnumeric spreadsheets which it did previously on 13.04.
Public bug reported:
I upgraded from Ubuntu 12.04 to 12.10. Gnumeric now does not open
certain gnumeric spreadsheets which it did previously on 12.04.
$ gdb gnumeric
GNU gdb (GDB) 7.6.1-ubuntu
[...]
(gdb) run
Starting program: /usr/bin/gnumeric
[...]
Program received signal SIGSEGV, Segmentatio
I'm using raring, I can not reproduce it any more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/664061
Title:
Wrong spacing between characters in form fields
Status in “evince” pack
I'm using raring, I can not reproduce it any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/664061
Title:
Wrong spacing between characters in form fields
To manage notifications about this bug
I'm using raring, I can not reproduce it any more.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/664061
Title:
Wrong spacing between characters in form fields
To manage notificati
Hi,
I have a complete Korean translation for this file:
http://bazaar.launchpad.net/~openintents-devs/openintents/translations/view/head:/translations_filemanager/ko.po
Please let me know how to get it to you so that it goes on the server.
Thanks,
Dennis
--
Mailing list: https://launchpad.net
Confirmed in Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/694762
Title:
mousetrap does not start natty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
** Description changed:
- Barrage does not open. A window pops open, and then a SIGABRT from a
- raise in /lib/x86_64-linux-gnu/libc.so.6 crashes the program.
+ Barrage does not open. A window pops open. Then a SIGABRT is raise()'d
+ from /lib/x86_64-linux-gnu/libc.so.6, crashing the program.
** Description changed:
- Barrage does not open. A window pops open, and then a SIGABRT from a
- raise in /lib/x86_64-linux-gnu/libc.so.6 crashes the program.
+ Barrage does not open. A window pops open. Then a SIGABRT is raise()'d
+ from /lib/x86_64-linux-gnu/libc.so.6, crashing the program.
** Tags added: precise
--
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is subscribed to barrage in Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Barrage does not open - crashes with SIGABRT
Status in “barrage” package in Ubuntu:
New
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Barrage does not open - crashes with SIGABRT
To manage notifications about this bug go to:
https://bugs.launchpad
Public bug reported:
Barrage does not open. A window pops open, and then a SIGABRT from a
raise in /lib/x86_64-linux-gnu/libc.so.6 crashes the program.
The stacktrace top in thread 1 is:
Stacktrace:
#0 0x7f7c1cbad445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info av
Public bug reported:
Barrage does not open. A window pops open, and then a SIGABRT from a
raise in /lib/x86_64-linux-gnu/libc.so.6 crashes the program.
The stacktrace top in thread 1 is:
Stacktrace:
#0 0x7f7c1cbad445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info av
Just like Adrian, it happened to me after opening the Dash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917974
Title:
unity-music-daemon crashed with SIGSEGV in g_bit_lock()
To manage notification
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
WLB - this is a duplicate of a previous bug. - bug #875557 . The
package with the problem is compiz-plugins-main . There is currently a
fix for this in oneiric-proposed . This web page -
https://wiki.ubuntu
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of compiz
packagers, which is
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I tried Raphael's suggestion. From a shell I ran "gconf-editor". Went to both
apps/compiz-1/plugins/expo/screen0/options/dnd_button
and
apps/compizconfig-1/profiles/plugins/expo/screen0/options/dnd_button
and changed from "Button1" to "Disabled".
Have not had a problem since.
This should be
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
ught of maybe
trying to pull some classes out of xmlbeans as well, as xmlbeans still
has 1503 classes. I will see how that goes.
Although this e-mail goes into it somewhat, I will be doing more work
on this this week and next week, and by the end of next week I'll open
a bug on this issue
Hi,
I wanted to see the POI HSSF/XSSF project on Android, so I did a port
to Android. I did a very basic spreadsheet, which can be seen here:
https://github.com/dennis-sheil/android-spreadsheet
The main reason the spreadsheet is so basic is that the first thing I
did was implement a very basic
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of compiz
packagers, which is
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 875557 ***
https://bugs.launchpad.net/bugs/875557
** This bug has been marked a duplicate of bug 875557
Compiz grid overlay appears after workspace switcher use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Bug watch added: GNOME Bug Tracker #656858
https://bugzilla.gnome.org/show_bug.cgi?id=656858
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=656858
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of De
** Bug watch added: GNOME Bug Tracker #656858
https://bugzilla.gnome.org/show_bug.cgi?id=656858
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=656858
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ub
** Bug watch added: GNOME Bug Tracker #656858
https://bugzilla.gnome.org/show_bug.cgi?id=656858
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=656858
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ub
"nfs shares are usually local"
We have a lot of ambiguity with the word local here, which is the entire
problem. I'm not sure what local means in "nfs shares are usually
local" - on the local host? On the same subnet? In the same location?
In the same organization? In the same city? Furthermo
"nfs shares are usually local"
We have a lot of ambiguity with the word local here, which is the entire
problem. I'm not sure what local means in "nfs shares are usually
local" - on the local host? On the same subnet? In the same location?
In the same organization? In the same city? Furthermo
"nfs shares are usually local"
We have a lot of ambiguity with the word local here, which is the entire
problem. I'm not sure what local means in "nfs shares are usually
local" - on the local host? On the same subnet? In the same location?
In the same organization? In the same city? Furthermo
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/293311
Title:
nautilus thumbnails files on a mounted NFS share
St
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/293311
Title:
nautilus thumbnails files on a mounted NFS share
To manage notific
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/293311
Title:
nautilus thumbnails files on a mounted NFS share
To manage notificat
Seeing this problem in Natty. Ajax's patch works for me, although
needing the following modifications in Natty due to the KdScreenInfo
data structure definition changing -
screen->fb[0].depth
screen->fb[0].bitsPerPixel
should be:
screen->fb.depth
screen->fb.bitsPerPixel
Xephyr would not launch
Seeing this problem in Natty. Ajax's patch works for me, although
needing the following modifications in Natty due to the KdScreenInfo
data structure definition changing -
screen->fb[0].depth
screen->fb[0].bitsPerPixel
should be:
screen->fb.depth
screen->fb.bitsPerPixel
Xephyr would not launch
The problem is it not with evince, but with the PDF. It is a bad PDF.
A file of the same name - http://gps-gimp-paint-
studio.googlecode.com/files/GPS_Gimp%20Paint%20Studio%201_2%20manual.pdf
, works properly. It is also identical with your file for the first
3047386 bytes, but your file imprope
The problem is it not with evince, but with the PDF. It is a bad PDF.
A file of the same name - http://gps-gimp-paint-
studio.googlecode.com/files/GPS_Gimp%20Paint%20Studio%201_2%20manual.pdf
, works properly. It is also identical with your file for the first
3047386 bytes, but your file imprope
** Changed in: evince (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744067
Title:
Not able to open PDF file.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
** Changed in: evince (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/744067
Title:
Not able to open PDF file.
--
desktop-bugs mailing list
d
> Dennis, this was marked as Triaged, sent upstream and if you look at
the upstream report the developers are working on it, so why [are you]
marking it as a duplicate of a non triaged one? [T]hat doesn't make
sense[,] please do not do it. The other bugs should be marked as a
duplicate of this one.
> Dennis, this was marked as Triaged, sent upstream and if you look at
the upstream report the developers are working on it, so why [are you]
marking it as a duplicate of a non triaged one? [T]hat doesn't make
sense[,] please do not do it. The other bugs should be marked as a
duplicate of this one.
*** This bug is a duplicate of bug 697095 ***
https://bugs.launchpad.net/bugs/697095
** This bug has been marked a duplicate of bug 697095
polkit-gnome-authentication-agent-1 crashed with SIGSEGV in
g_datalist_id_set_data_full() during logout
* You can subscribe to bug 697095 by following
** Bug watch added: GNOME Bug Tracker #643843
https://bugzilla.gnome.org/show_bug.cgi?id=643843
** Also affects: evince via
https://bugzilla.gnome.org/show_bug.cgi?id=643843
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubun
** Bug watch added: GNOME Bug Tracker #643843
https://bugzilla.gnome.org/show_bug.cgi?id=643843
** Also affects: evince via
https://bugzilla.gnome.org/show_bug.cgi?id=643843
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubun
With regards to iroli's comments...
With a fully update 10.10, I do a print to file of the the PDF given
(krimitotal_der_verfluchte...) If I print it to file as a PDF or
PostScript file, it seems OK. If I print it to file as an SVG, I get
the types of errors mentioned. It also seems to be the s
With regards to iroli's comments...
With a fully update 10.10, I do a print to file of the the PDF given
(krimitotal_der_verfluchte...) If I print it to file as a PDF or
PostScript file, it seems OK. If I print it to file as an SVG, I get
the types of errors mentioned. It also seems to be the s
bbordwell: cairo git commit e9c1f...a739c on October 29, 2010 fixed the
problem, perhaps inadvertently, for this PDF anyhow. When the cairo
people were notified today that this bug is in their last release
(1.10.2), but is fixed after the e9c1f...a739c commit, they took a look
at their code and pa
Chris Wilson posted a commit to cairo git master today that deals with
this error (
http://cgit.freedesktop.org/cairo/commit/?id=d558f40c44f3d4f4a8a613318ff556c5d26914f7
).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Actually I meant to say it was fixed on October 29th, 2010 in upstream,
the patch was written on October 16th, but was committed 13 days later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710072
Tit
This is a cairo bug. The bug has not been fixed in any cairo releases
as of yet, but it was fixed in cairo's git upstream on October 16, 2010
(commit e9c1fc31887c5bfbb7d086f923a7628b7cfa739c - "path: Do not access
flags directly"). This bug was reported for Ubuntu 10.10, but it
currently affects
** Package changed: poppler (Ubuntu) => cairo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710072
Title:
Evince crash showing the attached PDF after page 93
--
ubuntu-bugs mailing list
u
** Package changed: poppler (Ubuntu) => cairo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in ubuntu.
https://bugs.launchpad.net/bugs/710072
Title:
Evince crash showing the attached PDF after page 93
--
desktop
Epdfview, which depends on the poppler library, crashes on this page as
well. So it is not a problem with evince, but with poppler (or
poppler's dependency on cairo, or cairo's dependency on pixman,
nonetheless it is not more universal than evince and we are working our
way down the library depend
Epdfview, which depends on the poppler library, crashes on this page as
well. So it is not a problem with evince, but with poppler (or
poppler's dependency on cairo, or cairo's dependency on pixman,
nonetheless it is not more universal than evince and we are working our
way down the library depend
That "fatal internal error -100" message is coming from a library evince
depends on, libspectre. The "fatal internal error" message is fro the
libspectre-0.26 package, it is on line 47 of the file spectre-gs.c, a
line which you can see hit stepping through the program calls, or logic.
Libspectre
1 - 100 of 298 matches
Mail list logo
