[Bug 390508] Re: notify-send ignores the expire timeout parameter
There's also a use case for screenshot applications, like Salasaga, where the notification telling the user a screenshot is about to occur MUST be removed before the screenshot is taken. Otherwise, all the screenshots have the warning notification itself in them, as happened when notify-osd became the default. Which is why notify-osd not adhering to something that works fine with the previous (proper, working) implementation is really not scoring points. -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notify-send ignores the expire timeout parameter
Wow. They really have. They've marked the idea in the brainstorms site as not being acceptable, so we can't even use the standard mechanisms to actually measure demand. -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notify-send ignores the expire timeout parameter
Nice write up up Adrian, good work. :) Now, let's hope it gets approved by the moderators. -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notify-send ignores the expire timeout parameter
Sounds like we need someone to write this up as an idea for http://brainstorm.ubuntu.com, so that way we can vote on it and put some actual numbers around the demand a version that supports timeouts. Who wants to write it up? -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492388] Re: Cannot edit new text
** Changed in: salasaga Status: Fix Committed = Fix Released ** Changed in: salasaga (Ubuntu) Status: Fix Committed = Fix Released -- Cannot edit new text https://bugs.launchpad.net/bugs/492388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492388] Re: Cannot edit new text
Hi Vadim, This bug should now be fixed in the latest development snapshot: http://www.salasaga.org/downloads/alpha6_dev/salasaga_200912061441.tar.bz2 Do you still have the Ubuntu system around that it was reported on, to verify the fix? -- Cannot edit new text https://bugs.launchpad.net/bugs/492388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492388] Re: Cannot edit new text
** Changed in: salasaga Status: In Progress = Fix Committed ** Changed in: salasaga (Ubuntu) Status: Invalid = Fix Committed -- Cannot edit new text https://bugs.launchpad.net/bugs/492388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492388] Re: Cannot edit new text
** Changed in: salasaga Status: Confirmed = In Progress -- Cannot edit new text https://bugs.launchpad.net/bugs/492388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492388] Re: Cannot edit new text
Hi Vadim, This looks like a bug found yesterday (but not in LP yet), in that when a person removes all of the text in a layer and closes it, when they open the layer for editing it crashes at the first typed character. The bug in that case is caused by no having a default font set (coding problem on my part). That bug will be fixed before release of Alpha 6 proper (soon), as it's very serious and will probably affect other things internally too. ** Changed in: salasaga Status: New = Confirmed ** Changed in: salasaga Importance: Undecided = High ** Changed in: salasaga Assignee: (unassigned) = Justin Clift (justin-salasaga) ** Changed in: salasaga Milestone: None = 0.8.0-alpha6 -- Cannot edit new text https://bugs.launchpad.net/bugs/492388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notify-send ignores the expire timeout parameter
MPT: The fix for this appears to be a 12 line patch (including the blank lines) which has been submitted, and shown to work. Yet you guys are refusing to implement this (very simple) patch, which would enable apps with specific needs to continue working to full functionality. We've had to code a reduced functionality workaround that detects Notify-OSD, and makes use of a confirmation bubble approach instead in order to GET THE NOTIFCATION OFF THE SCREEN in time for the screenshot. But it makes for a lesser user experience. I'm obviously extremely unimpressed with the inflexible line you guys are taking on this. It really doesn't suit *100%* of software packages, and the code to allow the edge cases (like our app) to work is already available. Can't you guys just enable it and allow people to move on with coding more important stuff? -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notify-send ignores the expire timeout parameter
Ugh. When testing my application on Karmic, notification timeouts aren't working as *required* for my application to function. What a steaming pile. :( -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390508] Re: notify-send ignores the expire timeout parameter
As follow up confirmation, switching to notification-daemon and removing notify-osd works fine. We'll need to ensure our Ubuntu packages have a Depends on notification-daemon listed, and list notify-osd as a Conflict. Should solve the problem. :) -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408417] Re: No option to log in remotely via XDMCP
Ironically, an easy to use workaround for now is to install KDM (the KDE login manager). That gives the XDMCP option. -- No option to log in remotely via XDMCP https://bugs.launchpad.net/bugs/408417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338489] Re: AllowDeactivateGrabs is broken
Ouch. Just upgraded to Jaunty and went looking for how to deactivate screengrabs, hitting this exact problem. Does anyone have or know a workaround? This is critical core functionality for Salasaga, an eLearning creation package that's already available through Add/Remove. Without the ability to trigger screenshots of applications with menu's open, which this bug is preventing, there's no way to create effective how-to style screenshots. :( -- AllowDeactivateGrabs is broken https://bugs.launchpad.net/bugs/338489 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 228911] [NEW] package libgio-dev conflicts with libglib2.0-dev
Public bug reported: Binary package hint: libgio-dev Added libgio-dev using Synaptic. This system already had the latest patches applied today (and rebooted), so it looks like the fix released in #205260 isn't for this issue. ProblemType: Package Architecture: i386 Date: Sat May 10 16:42:45 2008 Dependencies: DistroRelease: Ubuntu 8.04 ErrorMessage: trying to overwrite `/usr/lib/pkgconfig/gio-2.0.pc', which is also in package libglib2.0-dev Package: libgio-dev None [modified: /var/lib/dpkg/info/libgio-dev.list] PackageArchitecture: i386 SourcePackage: gio-standalone Title: package libgio-dev None [modified: /var/lib/dpkg/info/libgio-dev.list] failed to install/upgrade: trying to overwrite `/usr/lib/pkgconfig/gio-2.0.pc', which is also in package libglib2.0-dev Uname: Linux 2.6.24-16-generic i686 ** Affects: gio-standalone (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package libgio-dev conflicts with libglib2.0-dev https://bugs.launchpad.net/bugs/228911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 228911] Re: package libgio-dev conflicts with libglib2.0-dev
** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/14416772/DpkgTerminalLog.txt -- package libgio-dev conflicts with libglib2.0-dev https://bugs.launchpad.net/bugs/228911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96094] Re: Problem upgrading xubuntu to 6.10 from 6.06
This is exactly the error that occurs when trying to upgrade a fresh 6.06.1 xubuntu install to 6.10. Steps: 1. Burned 6.06.1 to CD and installed it over a new, blank 160GB HDD. 2. Rebooted (first boot) 3. Ran update manager, it displayed 6.10 being available. Told it to upgrade. The above error occurs. :( -- Problem upgrading xubuntu to 6.10 from 6.06 https://bugs.launchpad.net/bugs/96094 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Hi, Mine was (probably) unusual, in that I upgraded a (newly installed and patched) 6.06 installation straight to 8.04. Did this because my father has a PC running 6.06, and he never receives the newer distribution available update notice when he runs the update manager. To see what might be going on, 6.06 got installed from CD into a VMware virtual machine, and then latest updates applied. Yep, he's right, there's no notification of a newer Ubuntu version being available. Instead, ran the command to check if there are any development versions that can be upgraded to, and it suggested 8.04 (pre release at the time). As this was a virtual machine I thought what the heck and let it proceed. Everything seemed ok afterwards except for the HAL initialisation failure error, that turned out to be because it wasn't in the rc levels after the upgrade. Hope that helps. :) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210382] Re: [needs-packaging] Salasaga
Hi guys, Initial working packages have been created for Hardy, Gutsy, and Feisty: http://sourceforge.net/project/showfiles.php?group_id=58083package_id=53841release_id=593793 No idea if they're up to proper packaging standards though. The meta files (control, copyright, rules, etc) are in Subversion here: http://salasaga.svn.sourceforge.net/viewvc/salasaga/trunk/packaging- files/ubuntu/debian/ Does someone have time to take a look at this? -- [needs-packaging] Salasaga https://bugs.launchpad.net/bugs/210382 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210382] Re: [needs-packaging] Salasaga
Hi, I'm the primary developer for Salasaga. Would recommend wait for at least a week or two before making packages for Salasaga. Due to the re-write of a major component (the time line widget), there is a lot of change happening in the code right at the moment. Although, to be fair, development snapshots are presently released every few days, and we'll soon be coming near to our first proper Alpha release. Would definitely recommend packaging Salasaga from the first proper Alpha release onwards though! Hope that helps. :) Regards and best wishes, Justin Clift -- [needs-packaging] Salasaga https://bugs.launchpad.net/bugs/210382 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Hi, I'm getting the Failed to initialize HAL error message after upgrading to 8.04 alpha last week. Running this in a VMware Workstation virtual machine for testing. Happens on every boot. Investigated a few options people mention on the forums, but nothing worked. Then looking at the /etc/rc2.d directory I noticed hal wasn't even listed! S12dbus - ../init.d/dbus S13gdm - ../init.d/gdm and no hal at all. Did a: $ sudo ln -s ../init.d/hal S15hal And rebooted, and now everything seems to start up properly. The CONCURRENCY level in /etc/init.d/rc hasn't been touched, it was already at none when I checked. Hope this helps. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
