Public bug reported:
Binary package hint: notification-daemon
Work has been going on to create a new backward-compatible version of
the notification spec: v0.10. This new spec makes it possible to share
notifications between KDE and GNOME.
Upstream is ok to merge the patches, but I don't think a
Public bug reported:
Updating from Jaunty to Karmic failed on initramfs-tools with this
error:
update-initramfs: Generating /boot/initrd.img-2.6.28-13-generic
cpio: ./lib/udev/vol_id: Cannot stat: No such file or directory
update-initramfs: failed for /boot/initrd.img-2.6.
The Kubuntu devs have been working on packaging a new version of the
plasmoid, but it was not fully satisfying :/. Have a look at bug 334052
and bug 330811, maybe the new version can help you nevertheless.
--
Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
https://bugs.laun
Hemanth wrote:
> Yes it's working fine :) , can we just get to know which part of the code
> was updated ?
Sure, here is the diff:
http://bazaar.launchpad.net/~agateau/notify-osd/no-bubble-in-
fullscreen/revision/328?start_revid=328&remember=326&compare_revid=326
--
NotifyOSD notifications shou
Aurélien Gâteau wrote:
> Ara Pulido wrote:
>> Steve, as Aurélien said, this is something the design team needs to
>> think about. Aurélien just shared his implementation and it is not
>> decided that this is going to be the actual behavior.
>
> Mmm... I think what Steve
Ara Pulido wrote:
> Steve, as Aurélien said, this is something the design team needs to
> think about. Aurélien just shared his implementation and it is not
> decided that this is going to be the actual behavior.
Mmm... I think what Steve means is that in my branch notifications are
also blocked i
I implemented fullscreen detection so that bubbles do not show up if
there is a fullscreen window, but I am not sure how to handle multi
monitor setups. We need input from the design team here.
If anyone is interested, the code can be downloaded with:
bzr get lp:~agateau/notify-osd/no-bubble-in-f
I was not asking to enter the hex key in your router, but in the dialog
shown by plasma-widget-network-manager. When I entered the wep key as
hex instead of ascii plasma-widget-network-manager connected
successfully.
--
Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
https:
I experienced the same problem. I have an access point with an ascii wep
key. I was able to make it run by entering the key in hexadecimal rather
than in ascii. Can you try to do so and see if it fixes the problem?
If you need help converting your key to hex, here is a small Python
trick I used:
... or use this updated patch.
** Attachment added: "Updated version of proposed patch"
http://launchpadlibrarian.net/24406382/02-avoid_potential_buffer_overrun.diff
--
Include libmsn in main
https://bugs.launchpad.net/bugs/308060
You received this bug notification because you are a member of
Please revert! As pointed out by Kees Cook, the patch is not correct.
As I said, I believe the patch is not needed, but if you are to include
this, then at least fix the switch() bug I introduced.
--
Include libmsn in main
https://bugs.launchpad.net/bugs/308060
You received this bug notification
Taking inspiration from KPassivePopup code, attached patch should fix
the problem.
** Attachment added:
"kubuntu_67_do_not_show_plasma_popups_over_screensaver.diff"
http://launchpadlibrarian.net/24365587/kubuntu_67_do_not_show_plasma_popups_over_screensaver.diff
--
notifications visible th
More on this. I wrote a simple test program to exercise the parser. I am
able to make toXMLStringUnSafe read past the source buffer end, but
strangely valgrind does not complain.
I also started to test the whole parser with strange strings. So far I
can't get it to crash or valgrind to complain. I
My patch is not fine (because of the switch case error I introduced).
What I meant is that _tcscpy() is only dangerous if either the source
buffer is not 0 terminated, or the source buffer is 0 terminated but the
destination buffer is too small.
After further inspection of the original code, I bel
Kees Cook wrote:
> On Fri, Mar 20, 2009 at 02:09:33PM -0000, Aurélien Gâteau wrote:
>> http://launchpadlibrarian.net/24149888/02-avoid_potential_buffer_overrun.diff
>
> "n" should be verified to be !=0, so that result[-1] isn't used.
[snip]
> This change does no
Here is a patch which changes the prototype of _tcscpy() to accept a
length parameter and adjust the code accordingly.
** Attachment added: "02-avoid_potential_buffer_overrun.diff"
http://launchpadlibrarian.net/24149888/02-avoid_potential_buffer_overrun.diff
--
Include libmsn in main
https://
I just tested it on x86. It works for me.
--
Please backport Wengophone 2.1 from Hardy to Feisty
https://bugs.launchpad.net/bugs/115223
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
301 - 317 of 317 matches
Mail list logo
