[Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
> Can you see if this solves the issue on your computers? I am pleased to report that this workaround fixes the problem for me. Thanks! (Xubuntu 14.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 469248] Re: [needs-packaging] Create package: Euphoria
There are several problems with this software: - It provides binaries conflicting with unix core utilities (ed) None of the binaries that euphoria provides really need to be in /usr/bin except exu The rest, (including ed) could remaing somewhere out of the path. - It requires an environment variable set to be used I think that instruction may be obsolete or Windows-only I have a working Euphoria installation with no EUDIR environment variable set. - It does not provide clear build instructions Amen to that! -- [needs-packaging] Create package: Euphoria https://bugs.launchpad.net/bugs/469248 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 357673] Re: No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42, R52
** Summary changed: - No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42 + No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42, R52 -- No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42, R52 https://bugs.launchpad.net/bugs/357673 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 198790] Re: picocom: incorrect default send command
It is also worth mentioning that the picocom man page claims that the default send command should be sz -vv -- picocom: incorrect default send command https://bugs.launchpad.net/bugs/198790 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 279923] Re: dosemu crashes if $_dosmem setting in dosemu.conf is changed
Oh! I should have clarified. I am not using the X windows mode of dosemu, I am running it in a text mode terminal. When you run in a terminal, it is not supposed to allocate the VGA graphics areas (leaving them available for $_dosmem) That is consistent with the behavior of real DOS. If you boot with a monochrome card (no VGA) you have access to more memory, or if you used the correct emm386 options you could disable your VGA card's graphics modes and get access to that memory. ** Description changed: Binary package hint: dosemu Description:Ubuntu 8.04.1 Release:8.04 Package version: dosemu 1.4.0+svn.1828-1 Dosemu has an option that controls available real-mode memory. Edit /etc/dosemu/dosemu.conf and you will find: # $_dosmem = (640) Uncomment this line, and slightly increase the number. 768 is the highest valid value, but 641 is sufficient to trigger this crash. - Run dosemu, and it will crash immediately with no error message. + Run dosemu (in console mode from a terminal, NOT the graphical X mode), + and it will crash immediately with no error message. This error does not occur when I downgrade to the older 1.2.2-9 packages. In my own configuration I use $_dosmem = (704) and it works perfectly in the older version. I have already worked around the LOWRAM mmap segmentation fault reported in bug 216398 -- dosemu crashes if $_dosmem setting in dosemu.conf is changed https://bugs.launchpad.net/bugs/279923 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 198351] Re: fusesmb - Not working properly.
I can reproduce this bug under two conditions. 1) If my network is not set up correctly, and it is impossible to connect to a MS networking server even with smbclient, then any attempt to use fusesmb (understandably) fails in exactly the way that Dr_Willis reports 2) If my network is set up correctly, and I CAN connect to MS networking servers as verified using smbclient, then my very first attempt to use fusesmb for a user always fails exactly as Dr_Willis has described, with the additional detail that ~/.smb/fusesmb.cache does not get created, but ~/.smb/fusesmb.cache.pid does get created. After approximately 5 minutes have passed, ~/.smb/fusesmb.cache.pid suddenly disappears and ~/.smb/fusesmb.cache suddenly appears. All subsequent attempts to use fusesmb work perfectly after that point, and the only way I can reproduce Dr_Willis's symptoms again is by manually deleting ~/.smb/fusesmb.cache -- fusesmb - Not working properly. https://bugs.launchpad.net/bugs/198351 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 279923] [NEW] dosemu crashes if $_dosmem setting in dosemu.conf is changed
Public bug reported: Binary package hint: dosemu Description:Ubuntu 8.04.1 Release:8.04 Package version: dosemu 1.4.0+svn.1828-1 Dosemu has an option that controls available real-mode memory. Edit /etc/dosemu/dosemu.conf and you will find: # $_dosmem = (640) Uncomment this line, and slightly increase the number. 768 is the highest valid value, but 641 is sufficient to trigger this crash. Run dosemu, and it will crash immediately with no error message. This error does not occur when I downgrade to the older 1.2.2-9 packages. In my own configuration I use $_dosmem = (704) and it works perfectly in the older version. I have already worked around the LOWRAM mmap segmentation fault reported in bug 216398 ** Affects: dosemu (Ubuntu) Importance: Undecided Status: New -- dosemu crashes if $_dosmem setting in dosemu.conf is changed https://bugs.launchpad.net/bugs/279923 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 146160] Re: [needs-packaging] btnx
I notice that buttons enabled through btnx can NOT be used to trigger compiz effect shortcuts :( On my Mac I can map button 6 to expose's show all windows but when I try to do the same with btnx for compiz's ctrl+alt+down shortcut, it does not work. -- [needs-packaging] btnx https://bugs.launchpad.net/bugs/146160 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
