Yeah, that is the next step, but I wanted to find out what code was
actually causing the crash so that I know who/what project to file the
bug with. Why bother glib people with something that is gnome-totem
territory? Besides, I think I have a pretty good idea of whats
happening here. It looks lik
After examining the evince source code and generating a few test pdf
files I don't think that this is a bug in evince at all. The program
just reports the internal document title given to it by the pdf file
itself. Documents generated by document converters or from software not
designed to properly
Ill give the specifics,
this code in evince (ev-window-title.c) sets the window title we see:
new_title = g_strdup_printf ("%s (%s)", *title, filename)
as you can see the format is "internal doc title (real filename)"
--
labels PDF document a microsoft word document
https://bugs.launchpad.net/bug
Funny thing... I tried to reproduce this crash from the command line
with /usr/bin/totem-video-thumbnailer -s 100x100 incomplete-and-being-
created.avi thumbnail.png and it worked fine, so I start nautilus and
the files are thumbnailed with no problem, so i guess I can no longer be
involved in this
These are very old reports that look like people with bad configurations
mostly. If there is still a problem with gdm in debian testing I think
there would be newer reports than 2005. Since testing is always changing
and there are no recent problems I suggest we close this report.
--
gdm fails to
I stupidly failed to notice that this is already rejected, but in the
launchpad listing of all the bugs it was listed as undecided and
unknown... sorry
--
gdm fails to start
https://bugs.launchpad.net/bugs/6931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This exists upstream at
http://bugzilla.gnome.org/show_bug.cgi?id=309856.
--
created .hidden folders/files stays visible after being moved/deleted
https://bugs.launchpad.net/bugs/28429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
This is not a bug. Readonly files that the user owns are deleted
normally. If you don't own the file you can't delete it unless the
permissions allow it.
--
Wastebasket fails with read only directories
https://bugs.launchpad.net/bugs/7560
You received this bug notification because you are a membe
Sorry, yes read only directorys cannot be removed even by the owner. I
will look into altering that dialog. I think something like "This
directory is marked as readonly, are you sure you want to remove it?"
would be more appropriate than the current "You do not have permission"
error esp. since it
Well really its just that gnome-vfs/nautilus is just informing you that
the permissions are set so that you can't delete said directory and not
offering to change them for you so they can be deleted. This is only an
issue with directories and not files (I am not sure why). File
permissions exist fo
Idea from post by Nikolaus Rath . Why don't we ask the user to
verify/input the detected physical size of the screen at installation
and automatically select a good DPI based on that and the screen
resolution? The configuration options for and changing the physical size
of the screen and DPI should
This is a problem for me unless I set Super to act as a key and not a
modifier. This is not the desired situation though. I would try to fix
this but i have no clue where to start. It is disconcerting that this
has been a bug for almost two years. Seems like a simple problem...
--
Metacity catchi
I believe I have found the document in question at http://www.cs.arizona.edu/classes/cs127a/spring07/HW/hw8-ElevatorBonanza.pdf";>this
address. I have seen this before actually, and never really thought
much of it. Maybe something to do with an odd PDF format? Will check
bugzilla tomorrow for a dup
I am currently checking whether this effects the current development
version of evince or if its just the 6.10(0.5.2) and
7.04(0.8.0)versions. Unfortunately I am currently working with a P2
350Mhz w/224MB ram (my main comp died) so compiles take forever. I will
be more productive when I get my new
It looks like the crash is actually occurring in gmain.c in libglib2.0-0
during a call to g_main_context_check(GMainContext* context, gint
max_priority, GPollFD* fds, gint n_fds). This is either a set of bad
args being passed or ??checking a NULL context??. If I could find out
what+where this was b
I believe I have found the document in question at http://www.cs.arizona.edu/classes/cs127a/spring07/HW/hw8-ElevatorBonanza.pdf";>this
address. I have seen this before actually, and never really thought
much of it. Maybe something to do with an odd PDF format? Will check
bugzilla tomorrow for a dup
I am currently checking whether this effects the current development
version of evince or if its just the 6.10(0.5.2) and
7.04(0.8.0)versions. Unfortunately I am currently working with a P2
350Mhz w/224MB ram (my main comp died) so compiles take forever. I will
be more productive when I get my new
It looks like the crash is actually occurring in gmain.c in libglib2.0-0
during a call to g_main_context_check(GMainContext* context, gint
max_priority, GPollFD* fds, gint n_fds). This is either a set of bad
args being passed or ??checking a NULL context??. If I could find out
what+where this was b
Yeah, that is the next step, but I wanted to find out what code was
actually causing the crash so that I know who/what project to file the
bug with. Why bother glib people with something that is gnome-totem
territory? Besides, I think I have a pretty good idea of whats
happening here. It looks lik
After examining the evince source code and generating a few test pdf
files I don't think that this is a bug in evince at all. The program
just reports the internal document title given to it by the pdf file
itself. Documents generated by document converters or from software not
designed to properly
Ill give the specifics,
this code in evince (ev-window-title.c) sets the window title we see:
new_title = g_strdup_printf ("%s (%s)", *title, filename)
as you can see the format is "internal doc title (real filename)"
--
labels PDF document a microsoft word document
https://bugs.launchpad.net/bug
Funny thing... I tried to reproduce this crash from the command line
with /usr/bin/totem-video-thumbnailer -s 100x100 incomplete-and-being-
created.avi thumbnail.png and it worked fine, so I start nautilus and
the files are thumbnailed with no problem, so i guess I can no longer be
involved in this
These are very old reports that look like people with bad configurations
mostly. If there is still a problem with gdm in debian testing I think
there would be newer reports than 2005. Since testing is always changing
and there are no recent problems I suggest we close this report.
--
gdm fails to
I stupidly failed to notice that this is already rejected, but in the
launchpad listing of all the bugs it was listed as undecided and
unknown... sorry
--
gdm fails to start
https://bugs.launchpad.net/bugs/6931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This exists upstream at
http://bugzilla.gnome.org/show_bug.cgi?id=309856.
--
created .hidden folders/files stays visible after being moved/deleted
https://bugs.launchpad.net/bugs/28429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
This is not a bug. Readonly files that the user owns are deleted
normally. If you don't own the file you can't delete it unless the
permissions allow it.
--
Wastebasket fails with read only directories
https://bugs.launchpad.net/bugs/7560
You received this bug notification because you are a membe
Sorry, yes read only directorys cannot be removed even by the owner. I
will look into altering that dialog. I think something like "This
directory is marked as readonly, are you sure you want to remove it?"
would be more appropriate than the current "You do not have permission"
error esp. since it
Well really its just that gnome-vfs/nautilus is just informing you that
the permissions are set so that you can't delete said directory and not
offering to change them for you so they can be deleted. This is only an
issue with directories and not files (I am not sure why). File
permissions exist fo
Idea from post by Nikolaus Rath . Why don't we ask the user to
verify/input the detected physical size of the screen at installation
and automatically select a good DPI based on that and the screen
resolution? The configuration options for and changing the physical size
of the screen and DPI should
This is a problem for me unless I set Super to act as a key and not a
modifier. This is not the desired situation though. I would try to fix
this but i have no clue where to start. It is disconcerting that this
has been a bug for almost two years. Seems like a simple problem...
--
Metacity catchi
I believe I have found the document in question at http://www.cs.arizona.edu/classes/cs127a/spring07/HW/hw8-ElevatorBonanza.pdf";>this
address. I have seen this before actually, and never really thought
much of it. Maybe something to do with an odd PDF format? Will check
bugzilla tomorrow for a dup
I am currently checking whether this effects the current development
version of evince or if its just the 6.10(0.5.2) and
7.04(0.8.0)versions. Unfortunately I am currently working with a P2
350Mhz w/224MB ram (my main comp died) so compiles take forever. I will
be more productive when I get my new
It looks like the crash is actually occurring in gmain.c in libglib2.0-0
during a call to g_main_context_check(GMainContext* context, gint
max_priority, GPollFD* fds, gint n_fds). This is either a set of bad
args being passed or ??checking a NULL context??. If I could find out
what+where this was b
Yeah, that is the next step, but I wanted to find out what code was
actually causing the crash so that I know who/what project to file the
bug with. Why bother glib people with something that is gnome-totem
territory? Besides, I think I have a pretty good idea of whats
happening here. It looks lik
After examining the evince source code and generating a few test pdf
files I don't think that this is a bug in evince at all. The program
just reports the internal document title given to it by the pdf file
itself. Documents generated by document converters or from software not
designed to properly
Ill give the specifics,
this code in evince (ev-window-title.c) sets the window title we see:
new_title = g_strdup_printf ("%s (%s)", *title, filename)
as you can see the format is "internal doc title (real filename)"
--
labels PDF document a microsoft word document
https://bugs.launchpad.net/bug
Funny thing... I tried to reproduce this crash from the command line
with /usr/bin/totem-video-thumbnailer -s 100x100 incomplete-and-being-
created.avi thumbnail.png and it worked fine, so I start nautilus and
the files are thumbnailed with no problem, so i guess I can no longer be
involved in this
These are very old reports that look like people with bad configurations
mostly. If there is still a problem with gdm in debian testing I think
there would be newer reports than 2005. Since testing is always changing
and there are no recent problems I suggest we close this report.
--
gdm fails to
I stupidly failed to notice that this is already rejected, but in the
launchpad listing of all the bugs it was listed as undecided and
unknown... sorry
--
gdm fails to start
https://bugs.launchpad.net/bugs/6931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This exists upstream at
http://bugzilla.gnome.org/show_bug.cgi?id=309856.
--
created .hidden folders/files stays visible after being moved/deleted
https://bugs.launchpad.net/bugs/28429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
This is not a bug. Readonly files that the user owns are deleted
normally. If you don't own the file you can't delete it unless the
permissions allow it.
--
Wastebasket fails with read only directories
https://bugs.launchpad.net/bugs/7560
You received this bug notification because you are a membe
Sorry, yes read only directorys cannot be removed even by the owner. I
will look into altering that dialog. I think something like "This
directory is marked as readonly, are you sure you want to remove it?"
would be more appropriate than the current "You do not have permission"
error esp. since it
Well really its just that gnome-vfs/nautilus is just informing you that
the permissions are set so that you can't delete said directory and not
offering to change them for you so they can be deleted. This is only an
issue with directories and not files (I am not sure why). File
permissions exist fo
Idea from post by Nikolaus Rath . Why don't we ask the user to
verify/input the detected physical size of the screen at installation
and automatically select a good DPI based on that and the screen
resolution? The configuration options for and changing the physical size
of the screen and DPI should
This is a problem for me unless I set Super to act as a key and not a
modifier. This is not the desired situation though. I would try to fix
this but i have no clue where to start. It is disconcerting that this
has been a bug for almost two years. Seems like a simple problem...
--
Metacity catchi
These are very old reports that look like people with bad configurations
mostly. If there is still a problem with gdm in debian testing I think
there would be newer reports than 2005. Since testing is always changing
and there are no recent problems I suggest we close this report.
--
gdm fails to
I stupidly failed to notice that this is already rejected, but in the
launchpad listing of all the bugs it was listed as undecided and
unknown... sorry
--
gdm fails to start
https://bugs.launchpad.net/bugs/6931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This exists upstream at
http://bugzilla.gnome.org/show_bug.cgi?id=309856.
--
created .hidden folders/files stays visible after being moved/deleted
https://bugs.launchpad.net/bugs/28429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
This is not a bug. Readonly files that the user owns are deleted
normally. If you don't own the file you can't delete it unless the
permissions allow it.
--
Wastebasket fails with read only directories
https://bugs.launchpad.net/bugs/7560
You received this bug notification because you are a membe
Sorry, yes read only directorys cannot be removed even by the owner. I
will look into altering that dialog. I think something like "This
directory is marked as readonly, are you sure you want to remove it?"
would be more appropriate than the current "You do not have permission"
error esp. since it
Well really its just that gnome-vfs/nautilus is just informing you that
the permissions are set so that you can't delete said directory and not
offering to change them for you so they can be deleted. This is only an
issue with directories and not files (I am not sure why). File
permissions exist fo
Idea from post by Nikolaus Rath . Why don't we ask the user to
verify/input the detected physical size of the screen at installation
and automatically select a good DPI based on that and the screen
resolution? The configuration options for and changing the physical size
of the screen and DPI should
This is a problem for me unless I set Super to act as a key and not a
modifier. This is not the desired situation though. I would try to fix
this but i have no clue where to start. It is disconcerting that this
has been a bug for almost two years. Seems like a simple problem...
--
Metacity catchi
I believe I have found the document in question at http://www.cs.arizona.edu/classes/cs127a/spring07/HW/hw8-ElevatorBonanza.pdf";>this
address. I have seen this before actually, and never really thought
much of it. Maybe something to do with an odd PDF format? Will check
bugzilla tomorrow for a dup
I am currently checking whether this effects the current development
version of evince or if its just the 6.10(0.5.2) and
7.04(0.8.0)versions. Unfortunately I am currently working with a P2
350Mhz w/224MB ram (my main comp died) so compiles take forever. I will
be more productive when I get my new
It looks like the crash is actually occurring in gmain.c in libglib2.0-0
during a call to g_main_context_check(GMainContext* context, gint
max_priority, GPollFD* fds, gint n_fds). This is either a set of bad
args being passed or ??checking a NULL context??. If I could find out
what+where this was b
Yeah, that is the next step, but I wanted to find out what code was
actually causing the crash so that I know who/what project to file the
bug with. Why bother glib people with something that is gnome-totem
territory? Besides, I think I have a pretty good idea of whats
happening here. It looks lik
After examining the evince source code and generating a few test pdf
files I don't think that this is a bug in evince at all. The program
just reports the internal document title given to it by the pdf file
itself. Documents generated by document converters or from software not
designed to properly
Ill give the specifics,
this code in evince (ev-window-title.c) sets the window title we see:
new_title = g_strdup_printf ("%s (%s)", *title, filename)
as you can see the format is "internal doc title (real filename)"
--
labels PDF document a microsoft word document
https://bugs.launchpad.net/bug
Funny thing... I tried to reproduce this crash from the command line
with /usr/bin/totem-video-thumbnailer -s 100x100 incomplete-and-being-
created.avi thumbnail.png and it worked fine, so I start nautilus and
the files are thumbnailed with no problem, so i guess I can no longer be
involved in this
These are very old reports that look like people with bad configurations
mostly. If there is still a problem with gdm in debian testing I think
there would be newer reports than 2005. Since testing is always changing
and there are no recent problems I suggest we close this report.
--
gdm fails to
I stupidly failed to notice that this is already rejected, but in the
launchpad listing of all the bugs it was listed as undecided and
unknown... sorry
--
gdm fails to start
https://bugs.launchpad.net/bugs/6931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This exists upstream at
http://bugzilla.gnome.org/show_bug.cgi?id=309856.
--
created .hidden folders/files stays visible after being moved/deleted
https://bugs.launchpad.net/bugs/28429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
This is not a bug. Readonly files that the user owns are deleted
normally. If you don't own the file you can't delete it unless the
permissions allow it.
--
Wastebasket fails with read only directories
https://bugs.launchpad.net/bugs/7560
You received this bug notification because you are a membe
Sorry, yes read only directorys cannot be removed even by the owner. I
will look into altering that dialog. I think something like "This
directory is marked as readonly, are you sure you want to remove it?"
would be more appropriate than the current "You do not have permission"
error esp. since it
Well really its just that gnome-vfs/nautilus is just informing you that
the permissions are set so that you can't delete said directory and not
offering to change them for you so they can be deleted. This is only an
issue with directories and not files (I am not sure why). File
permissions exist fo
Idea from post by Nikolaus Rath . Why don't we ask the user to
verify/input the detected physical size of the screen at installation
and automatically select a good DPI based on that and the screen
resolution? The configuration options for and changing the physical size
of the screen and DPI should
This is a problem for me unless I set Super to act as a key and not a
modifier. This is not the desired situation though. I would try to fix
this but i have no clue where to start. It is disconcerting that this
has been a bug for almost two years. Seems like a simple problem...
--
Metacity catchi
I believe I have found the document in question at http://www.cs.arizona.edu/classes/cs127a/spring07/HW/hw8-ElevatorBonanza.pdf";>this
address. I have seen this before actually, and never really thought
much of it. Maybe something to do with an odd PDF format? Will check
bugzilla tomorrow for a dup
I am currently checking whether this effects the current development
version of evince or if its just the 6.10(0.5.2) and
7.04(0.8.0)versions. Unfortunately I am currently working with a P2
350Mhz w/224MB ram (my main comp died) so compiles take forever. I will
be more productive when I get my new
It looks like the crash is actually occurring in gmain.c in libglib2.0-0
during a call to g_main_context_check(GMainContext* context, gint
max_priority, GPollFD* fds, gint n_fds). This is either a set of bad
args being passed or ??checking a NULL context??. If I could find out
what+where this was b
Yeah, that is the next step, but I wanted to find out what code was
actually causing the crash so that I know who/what project to file the
bug with. Why bother glib people with something that is gnome-totem
territory? Besides, I think I have a pretty good idea of whats
happening here. It looks lik
After examining the evince source code and generating a few test pdf
files I don't think that this is a bug in evince at all. The program
just reports the internal document title given to it by the pdf file
itself. Documents generated by document converters or from software not
designed to properly
Ill give the specifics,
this code in evince (ev-window-title.c) sets the window title we see:
new_title = g_strdup_printf ("%s (%s)", *title, filename)
as you can see the format is "internal doc title (real filename)"
--
labels PDF document a microsoft word document
https://bugs.launchpad.net/bug
Funny thing... I tried to reproduce this crash from the command line
with /usr/bin/totem-video-thumbnailer -s 100x100 incomplete-and-being-
created.avi thumbnail.png and it worked fine, so I start nautilus and
the files are thumbnailed with no problem, so i guess I can no longer be
involved in this
These are very old reports that look like people with bad configurations
mostly. If there is still a problem with gdm in debian testing I think
there would be newer reports than 2005. Since testing is always changing
and there are no recent problems I suggest we close this report.
--
gdm fails to
I stupidly failed to notice that this is already rejected, but in the
launchpad listing of all the bugs it was listed as undecided and
unknown... sorry
--
gdm fails to start
https://bugs.launchpad.net/bugs/6931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This exists upstream at
http://bugzilla.gnome.org/show_bug.cgi?id=309856.
--
created .hidden folders/files stays visible after being moved/deleted
https://bugs.launchpad.net/bugs/28429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
This is not a bug. Readonly files that the user owns are deleted
normally. If you don't own the file you can't delete it unless the
permissions allow it.
--
Wastebasket fails with read only directories
https://bugs.launchpad.net/bugs/7560
You received this bug notification because you are a membe
Sorry, yes read only directorys cannot be removed even by the owner. I
will look into altering that dialog. I think something like "This
directory is marked as readonly, are you sure you want to remove it?"
would be more appropriate than the current "You do not have permission"
error esp. since it
Well really its just that gnome-vfs/nautilus is just informing you that
the permissions are set so that you can't delete said directory and not
offering to change them for you so they can be deleted. This is only an
issue with directories and not files (I am not sure why). File
permissions exist fo
Idea from post by Nikolaus Rath . Why don't we ask the user to
verify/input the detected physical size of the screen at installation
and automatically select a good DPI based on that and the screen
resolution? The configuration options for and changing the physical size
of the screen and DPI should
This is a problem for me unless I set Super to act as a key and not a
modifier. This is not the desired situation though. I would try to fix
this but i have no clue where to start. It is disconcerting that this
has been a bug for almost two years. Seems like a simple problem...
--
Metacity catchi
I believe I have found the document in question at http://www.cs.arizona.edu/classes/cs127a/spring07/HW/hw8-ElevatorBonanza.pdf";>this
address. I have seen this before actually, and never really thought
much of it. Maybe something to do with an odd PDF format? Will check
bugzilla tomorrow for a dup
I am currently checking whether this effects the current development
version of evince or if its just the 6.10(0.5.2) and
7.04(0.8.0)versions. Unfortunately I am currently working with a P2
350Mhz w/224MB ram (my main comp died) so compiles take forever. I will
be more productive when I get my new
It looks like the crash is actually occurring in gmain.c in libglib2.0-0
during a call to g_main_context_check(GMainContext* context, gint
max_priority, GPollFD* fds, gint n_fds). This is either a set of bad
args being passed or ??checking a NULL context??. If I could find out
what+where this was b
Yeah, that is the next step, but I wanted to find out what code was
actually causing the crash so that I know who/what project to file the
bug with. Why bother glib people with something that is gnome-totem
territory? Besides, I think I have a pretty good idea of whats
happening here. It looks lik
After examining the evince source code and generating a few test pdf
files I don't think that this is a bug in evince at all. The program
just reports the internal document title given to it by the pdf file
itself. Documents generated by document converters or from software not
designed to properly
Ill give the specifics,
this code in evince (ev-window-title.c) sets the window title we see:
new_title = g_strdup_printf ("%s (%s)", *title, filename)
as you can see the format is "internal doc title (real filename)"
--
labels PDF document a microsoft word document
https://bugs.launchpad.net/bug
Funny thing... I tried to reproduce this crash from the command line
with /usr/bin/totem-video-thumbnailer -s 100x100 incomplete-and-being-
created.avi thumbnail.png and it worked fine, so I start nautilus and
the files are thumbnailed with no problem, so i guess I can no longer be
involved in this
90 matches
Mail list logo
