Attached is a diff that highlights the change that needs to be made in
the debian/postinst script in flashplugin-
nonfree_9.0.48.0.0ubuntu8_amd64.deb package. Please note that the bug
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 must
also be fixed for nspluginwrapper to work prop
On a side note, but relevant just the same, the problem with
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 seems to
an easy fix also. I haven't looked at the package really as I am not
sure what package to look at here, but I know that copying
libXcomposite.so.1.0.0 and the soname
Very sorry, i didn't read this really, I was in a hurry. I didn't see
the patch already submitted. The fix I provided (along with the ia-32
workaround) did, however, fix this on my system.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug
Alright Pär, I will take your word for it that the install path is incorrect. I
just caught the -n because on my system using that option with nspluginwrapper
causes an error and a usage message. the output is as such:
[EMAIL PROTECTED] NSPLUGIN_DIR=/var/lib/flashplugin-nonfree/
/usr/bin/nsplugi
I have not read this page in full because i don't have time, so please
forgive me for posting things that have already been said. I am coming
to this bug from a problem with another package that is affected. I am
not intending to provide some ground breaking news, just verify what has
already been
I notice that after today's update to flashplugin-
nonfree-9.0.48.0.0ubuntu9 we still have the invalid argument to
nspluginwrapper error.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug notification because you are a member of Ubuntu
Bu
I reinstalled the nspluginwrapper package and problem solved. Strange.
Well I am not sure how that happened, but you can understand my mistake
the wrong binary being installed and all. Sorry about that.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You rec
The diffs discribed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184197
fixed this problem for me in the debian package. It should work the same for
Ubuntu. I don't see how this bug is still relavent actually.
--
Info pages installed incorrectly
https://launchpad.net/bugs/4883
--
ubunt
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
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
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
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
Bugs, which is a
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
Bugs, which is a direct subscriber.
--
u
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
Could we maybe get the relavent /etc/X11/xorg.conf and
/var/log/Xorg.*.log files. I think this would help determine the
graphics cards driver status. This is likely not be the issue, but it is
nice to get it out of the way. I have noticed a bit of instability with
compiz 0.3.6 myself, just not this
I am not sure that this is a bug. Maybe put it on the wish list. If it is an
Image issue it is a matter of "It would be nice if..." and if it is an issue
with the development status of the open source
nvidia driver then it is still an issue of not having a desired feature (ie.
better image rende
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
Have you tried compiling the coretemp module source against the Ubuntu
2.6.20-generic headers or applying this patch to the Ubuntu kernel
source? Easier than compiling and maintaining a homebrew kernel.
--
centrino duo sensors need a kernel patch
https://bugs.launchpad.net/bugs/115386
You receive
On another note: Does synaptic (in System -> Administration -> Synaptic)
still work or is it just the Add/Remove and Update manager?
--
add or remove applications not working
https://bugs.launchpad.net/bugs/115619
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Do you recall what those last packages you installed were? I have
updated my system and have no issues yet, but your system may have
broken some other way.
--
add or remove applications not working
https://bugs.launchpad.net/bugs/115619
You received this bug notification because you are a member
This is fixed in >= 2.5.0 and will not be back ported, should we do it
ourselves or just upgrade to 2.5.0 (or 2.5.2 soon) as it is available
now?
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://bugs.launchpad.net/bugs/76396
You received this bug notification bec
IMHO we might just consider upgrading even though Debian hasn't yet,
they would likely accept the new version soon after we upgrade.
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://bugs.launchpad.net/bugs/76396
You received this bug notification because you are
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
The diffs discribed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184197
fixed this problem for me in the debian package. It should work the same for
Ubuntu. I don't see how this bug is still relavent actually.
--
Info pages installed incorrectly
https://launchpad.net/bugs/4883
--
ubunt
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
Bugs, which is a
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
Bugs, which is a direct subscriber.
--
u
Attached is a diff that highlights the change that needs to be made in
the debian/postinst script in flashplugin-
nonfree_9.0.48.0.0ubuntu8_amd64.deb package. Please note that the bug
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 must
also be fixed for nspluginwrapper to work prop
On a side note, but relevant just the same, the problem with
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 seems to
an easy fix also. I haven't looked at the package really as I am not
sure what package to look at here, but I know that copying
libXcomposite.so.1.0.0 and the soname
Very sorry, i didn't read this really, I was in a hurry. I didn't see
the patch already submitted. The fix I provided (along with the ia-32
workaround) did, however, fix this on my system.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug
Alright Pär, I will take your word for it that the install path is incorrect. I
just caught the -n because on my system using that option with nspluginwrapper
causes an error and a usage message. the output is as such:
[EMAIL PROTECTED] NSPLUGIN_DIR=/var/lib/flashplugin-nonfree/
/usr/bin/nsplugi
I have not read this page in full because i don't have time, so please
forgive me for posting things that have already been said. I am coming
to this bug from a problem with another package that is affected. I am
not intending to provide some ground breaking news, just verify what has
already been
I notice that after today's update to flashplugin-
nonfree-9.0.48.0.0ubuntu9 we still have the invalid argument to
nspluginwrapper error.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug notification because you are a member of Ubuntu
Bu
I reinstalled the nspluginwrapper package and problem solved. Strange.
Well I am not sure how that happened, but you can understand my mistake
the wrong binary being installed and all. Sorry about that.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You rec
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
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
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
This is fixed in >= 2.5.0 and will not be back ported, should we do it
ourselves or just upgrade to 2.5.0 (or 2.5.2 soon) as it is available
now?
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://bugs.launchpad.net/bugs/76396
You received this bug notification bec
IMHO we might just consider upgrading even though Debian hasn't yet,
they would likely accept the new version soon after we upgrade.
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://bugs.launchpad.net/bugs/76396
You received this bug notification because you are
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
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
Could we maybe get the relavent /etc/X11/xorg.conf and
/var/log/Xorg.*.log files. I think this would help determine the
graphics cards driver status. This is likely not be the issue, but it is
nice to get it out of the way. I have noticed a bit of instability with
compiz 0.3.6 myself, just not this
I am not sure that this is a bug. Maybe put it on the wish list. If it is an
Image issue it is a matter of "It would be nice if..." and if it is an issue
with the development status of the open source
nvidia driver then it is still an issue of not having a desired feature (ie.
better image rende
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
Have you tried compiling the coretemp module source against the Ubuntu
2.6.20-generic headers or applying this patch to the Ubuntu kernel
source? Easier than compiling and maintaining a homebrew kernel.
--
centrino duo sensors need a kernel patch
https://bugs.launchpad.net/bugs/115386
You receive
On another note: Does synaptic (in System -> Administration -> Synaptic)
still work or is it just the Add/Remove and Update manager?
--
add or remove applications not working
https://bugs.launchpad.net/bugs/115619
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Do you recall what those last packages you installed were? I have
updated my system and have no issues yet, but your system may have
broken some other way.
--
add or remove applications not working
https://bugs.launchpad.net/bugs/115619
You received this bug notification because you are a member
Attached is a diff that highlights the change that needs to be made in
the debian/postinst script in flashplugin-
nonfree_9.0.48.0.0ubuntu8_amd64.deb package. Please note that the bug
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 must
also be fixed for nspluginwrapper to work prop
On a side note, but relevant just the same, the problem with
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 seems to
an easy fix also. I haven't looked at the package really as I am not
sure what package to look at here, but I know that copying
libXcomposite.so.1.0.0 and the soname
Very sorry, i didn't read this really, I was in a hurry. I didn't see
the patch already submitted. The fix I provided (along with the ia-32
workaround) did, however, fix this on my system.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug
Alright Pär, I will take your word for it that the install path is incorrect. I
just caught the -n because on my system using that option with nspluginwrapper
causes an error and a usage message. the output is as such:
[EMAIL PROTECTED] NSPLUGIN_DIR=/var/lib/flashplugin-nonfree/
/usr/bin/nsplugi
I have not read this page in full because i don't have time, so please
forgive me for posting things that have already been said. I am coming
to this bug from a problem with another package that is affected. I am
not intending to provide some ground breaking news, just verify what has
already been
I notice that after today's update to flashplugin-
nonfree-9.0.48.0.0ubuntu9 we still have the invalid argument to
nspluginwrapper error.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug notification because you are a member of Ubuntu
Bu
I reinstalled the nspluginwrapper package and problem solved. Strange.
Well I am not sure how that happened, but you can understand my mistake
the wrong binary being installed and all. Sorry about that.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You rec
The diffs discribed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184197
fixed this problem for me in the debian package. It should work the same for
Ubuntu. I don't see how this bug is still relavent actually.
--
Info pages installed incorrectly
https://launchpad.net/bugs/4883
--
ubunt
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
Bugs, which is a
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
Bugs, which is a direct subscriber.
--
u
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
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
Could we maybe get the relavent /etc/X11/xorg.conf and
/var/log/Xorg.*.log files. I think this would help determine the
graphics cards driver status. This is likely not be the issue, but it is
nice to get it out of the way. I have noticed a bit of instability with
compiz 0.3.6 myself, just not this
I am not sure that this is a bug. Maybe put it on the wish list. If it is an
Image issue it is a matter of "It would be nice if..." and if it is an issue
with the development status of the open source
nvidia driver then it is still an issue of not having a desired feature (ie.
better image rende
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
Have you tried compiling the coretemp module source against the Ubuntu
2.6.20-generic headers or applying this patch to the Ubuntu kernel
source? Easier than compiling and maintaining a homebrew kernel.
--
centrino duo sensors need a kernel patch
https://bugs.launchpad.net/bugs/115386
You receive
On another note: Does synaptic (in System -> Administration -> Synaptic)
still work or is it just the Add/Remove and Update manager?
--
add or remove applications not working
https://bugs.launchpad.net/bugs/115619
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Do you recall what those last packages you installed were? I have
updated my system and have no issues yet, but your system may have
broken some other way.
--
add or remove applications not working
https://bugs.launchpad.net/bugs/115619
You received this bug notification because you are a member
This is fixed in >= 2.5.0 and will not be back ported, should we do it
ourselves or just upgrade to 2.5.0 (or 2.5.2 soon) as it is available
now?
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://bugs.launchpad.net/bugs/76396
You received this bug notification bec
IMHO we might just consider upgrading even though Debian hasn't yet,
they would likely accept the new version soon after we upgrade.
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://bugs.launchpad.net/bugs/76396
You received this bug notification because you are
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
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
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
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
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
The diffs discribed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184197
fixed this problem for me in the debian package. It should work the same for
Ubuntu. I don't see how this bug is still relavent actually.
--
Info pages installed incorrectly
https://launchpad.net/bugs/4883
--
ubunt
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
Attached is a diff that highlights the change that needs to be made in
the debian/postinst script in flashplugin-
nonfree_9.0.48.0.0ubuntu8_amd64.deb package. Please note that the bug
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 must
also be fixed for nspluginwrapper to work prop
On a side note, but relevant just the same, the problem with
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/138145 seems to
an easy fix also. I haven't looked at the package really as I am not
sure what package to look at here, but I know that copying
libXcomposite.so.1.0.0 and the soname
Very sorry, i didn't read this really, I was in a hurry. I didn't see
the patch already submitted. The fix I provided (along with the ia-32
workaround) did, however, fix this on my system.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug
Alright Pär, I will take your word for it that the install path is incorrect. I
just caught the -n because on my system using that option with nspluginwrapper
causes an error and a usage message. the output is as such:
[EMAIL PROTECTED] NSPLUGIN_DIR=/var/lib/flashplugin-nonfree/
/usr/bin/nsplugi
I have not read this page in full because i don't have time, so please
forgive me for posting things that have already been said. I am coming
to this bug from a problem with another package that is affected. I am
not intending to provide some ground breaking news, just verify what has
already been
I notice that after today's update to flashplugin-
nonfree-9.0.48.0.0ubuntu9 we still have the invalid argument to
nspluginwrapper error.
--
gutsy amd64: flashplugin-nonfree not working
https://bugs.launchpad.net/bugs/133452
You received this bug notification because you are a member of Ubuntu
Bu
1 - 100 of 180 matches
Mail list logo
