[Bug 1584539] [NEW] 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault
Public bug reported: In 14.04, an exception in the ruby code of a plugin caused the error to be printed to stderr, after which vim would launch, skipping the offending plugin: Error detected while processing /mnt/terra/home/simon/dev/vim-livecoding/plugin/livecoding.vim: line 37: NameError: undefined local variable or method `undefined_method_causing_an_exception' for main:Object Press ENTER or type command to continue But in 16.04, the same thing causes vim to segfault: Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault (core dumped) --- Vim version in 14.04: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:59) Included patches: 1-52 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by buildd@ Huge version with GTK2 GUI. Vim version in 16.04: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version with GTK2 GUI. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vim-gtk 2:7.4.1689-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 22 22:33:45 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-04-25 (392 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to xenial on 2016-05-22 (0 days ago) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584539 Title: 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1584539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979880] Re: Skype causes almost-full lockup after 30 minutes of operation
Annoyingly, for the past week I hadn't had this problem at all. (Well, good for me, but annoying for bug-fixing purposes). I've just upgraded to 4.0 today, and it seems to be fine, but I don't know if that's because it's actually fixed, or if it's just that whatever changed a week ago meant I'm no longer affected. Sorry that isn't more helpful. All I can do is report back if it ever starts happening again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979880 Title: Skype causes almost-full lockup after 30 minutes of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/skype/+bug/979880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979880] Re: Skype causes almost-full lockup after 30 minutes of operation
Funnily enough, I only started having this problem after I upgraded to 12.04. A few more details: - The system starts reacting very slowly because skype is using up all available system memory almost immediately after you log in to it. (Note: it is on log-in, not actually starting skype; disable automatic log-in to prove it). - After some minutes, skype crashes with an out of memory error. - Subsequently starting skype it runs without problems - the problem only happens the first time skype starts on a cold boot. - The problem occurs with both the version of skype in the repositories, and the deb available from skype.com. - There's a thread on the skype forums about this bug, with several guesses as to the cause and suggested workarounds: http://community.skype.com/t5/Linux/Skype-eats-all-system-memory- Linux/td-p/222 Simon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979880 Title: Skype causes almost-full lockup after 30 minutes of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/skype/+bug/979880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 938758] Re: AutoHidden launcher reveal sensitivity adjustment should allow disabling push-past for wacom tablets
Using a Wacom Volito2 on 12.04 beta 2, icb410's workaround - setting the Launcher Reveal Pressure setting to 1 in - doesn't work for me. I've tried fiddling about with the settings in ccsm, but can't find any combination that makes the launcher respond to the tablet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938758 Title: AutoHidden launcher reveal sensitivity adjustment should allow disabling push-past for wacom tablets To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/938758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740767] Re: gtk-window-decorator crashed with SIGSEGV in gwd_get_decor_frame()
The only thing I've found that works to get around the problem that the old, broken setting (gtk-window-decorator) replacing the correct one (compiz-decorator) whenever you log out in is actually manually making /usr/bin/gtk-window-decorator a symlink to /usr/bin/compiz-decorator. Not a particularly pretty workaround, but at least I can use window menus now... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740767 Title: gtk-window-decorator crashed with SIGSEGV in gwd_get_decor_frame() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515275] Re: Kernel panic when I remove USB wi-fi stick 'D-link DWL-G122'
Thanks for your reply. Forgive me if I seem rude, but I'm not really sure how I can usefully respond to a copied-and-pasted response asking that I see if the bug is still there on Karmic and attach apport debug information, when my original report shows that I am already running Karmic (and you, in fact, added the tag karmic to the report), and apport information is clearly already attached. Does anyone know if there's some way to get any debug information out of a kernel panic on Ubuntu? The Ubuntu kernel panic page (https://help.ubuntu.com/community/KernelPanic) is useless, and standard guides usually either assume you're in text mode and can read debug information printed to the terminal, or involve connecting an external terminal to a serial port (not practical, for obvious reasons). -- Kernel panic when I remove USB wi-fi stick 'D-link DWL-G122' https://bugs.launchpad.net/bugs/515275 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 515275] [NEW] Kernel panic when I remove USB wi-fi stick 'D-link DWL-G122'
Public bug reported: The above USB wi-fi dongle (D-link DWL-G122) usually works fine. But occasionally it stops working (lights go off, I'm disconnected, error messages like rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x0410 with error -110 printed in kern.log and syslog). It used to be the case that unplugging it and plugging it back in when this happens made it start working again. But in Karmic, unplugging it sometimes causes a kernel panic. At least, I assume it's a kernel panic -- no messages are written in any of the log files (the last entry is usually one of the rt2x00 messages above), but the display freezes, and alt+sysrq+REISUB (which I've never had fail before) has no effect. On Karmic, with the latest kernel. ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 2424 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 [SB0060] (rev.7, serial:0x80611102) at 0x7000, irq 19' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 224 Simple ctrls : 45 Date: Sun Jan 31 21:29:02 2010 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=c42479fc-ae74-4886-a34a-90848fe3556e Package: linux-image-2.6.31-17-generic 2.6.31-17.54 ProcCmdLine: root=UUID=7e814db4-ef85-4852-bdef-6264ff3cff4d ro splash ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic RelatedPackageVersions: linux-backports-modules-2.6.31-17-generic N/A linux-firmware 1.25 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Uname: Linux 2.6.31-17-generic i686 WpaSupplicantLog: dmi.bios.date: 05/30/2003 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: nVidia-nForce2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd05/30/2003:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnnVidia-nForce2:rvr:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Kernel panic when I remove USB wi-fi stick 'D-link DWL-G122' https://bugs.launchpad.net/bugs/515275 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 515275] Re: Kernel panic when I remove USB wi-fi stick 'D-link DWL-G122'
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/38591093/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/38591094/AplayDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/38591095/ArecordDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/38591096/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/38591097/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt http://launchpadlibrarian.net/38591098/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt http://launchpadlibrarian.net/38591099/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/38591100/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/38591101/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/38591103/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/38591104/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/38591105/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/38591106/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/38591107/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/38591108/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/38591109/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/38591110/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/3859/UdevLog.txt ** Attachment added: UserAsoundrc.txt http://launchpadlibrarian.net/38591112/UserAsoundrc.txt ** Attachment added: WifiSyslog.gz http://launchpadlibrarian.net/38591113/WifiSyslog.gz ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/38591114/XsessionErrors.txt -- Kernel panic when I remove USB wi-fi stick 'D-link DWL-G122' https://bugs.launchpad.net/bugs/515275 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 456530] Re: empathy crashed with SIGILL
This just happened to me, with pidgin (worked fine yesterday, broken today, weirdly); upgrading gavl fixed it. (Ubuntu 9.10, fully up to date) -- empathy crashed with SIGILL https://bugs.launchpad.net/bugs/456530 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 395537] [NEW] Wacom tablet stops working after hibernation
Public bug reported: After hibernating and resuming, my Wacom (Volito2, CTF-420) tablet does not work. It continues not to work even after restarting X; a reboot is needed to make it work again. Running Ubuntu 9.04, with wacom-tools and xserver-xorg-input-wacom both at version 1:0.8.2.2-0ubuntu2. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: hibernation wacom -- Wacom tablet stops working after hibernation https://bugs.launchpad.net/bugs/395537 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 395537] Re: Wacom tablet stops working after hibernation
** Attachment added: The relevent part of kern.log http://launchpadlibrarian.net/28687650/kern.log ** Tags removed: hibernating -- Wacom tablet stops working after hibernation https://bugs.launchpad.net/bugs/395537 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 180866] Re: [XPS M1330] Eject Button Doesn't Work
This is still a problem in Jaunty, and it's not specific to Dell laptops either: I have the same problem on my (completely generic, self-built, with generic DVD drive) desktop. To summarise: the eject button works fine if no disc is in the drive or if one is in the drive but not mounted. If a mounted disc is in there, it has no effect. I'm also reopening it. The idea that nothing can be done about it is surely wrong: Most Linux distros (including, as Rene Horn poitns out above, Ubuntu in days past), not to mention Windows, apparently handle the eject button perfectly fine. So there certainly can't be a fundamental reason it is impossible to make it work as users expect. No? ** Changed in: ubuntu Status: Invalid = Confirmed -- [XPS M1330] Eject Button Doesn't Work https://bugs.launchpad.net/bugs/180866 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 341389] Re: gnome-open keeps re-running itself if set as default opening application
Confirmed. I've just been hit by this myself (on Intrepid). It took about half an hour to work out that it was gnome-open, because neither top, nor htop, nor gnome-system-monitor were any use at all. All three showed 100% total CPU usage, but none showed what was using it: adding up the CPU totals for all processes usually came to about 10%. gnome-open, on recausing the problem and checking now, was right at the bottom, shown using up no CPU whatsoever. I only finally worked out that it was gnome-open using atop: using the 'c' (show command line) option showed a large number of gnome-open lines. The brackets indicate that the process finished during the last interval apparently: it was restarting itself over and over, but only one copy was ever running at one time; hence why top and htop only showed one. So how did this happen? At some point, I think I set Opera to display shell scripts with gnome-open, in the belief that this would just cause it to open them with Gnome's default handler (which at the time was gedit). Apparently that must have caused gnome-open to be set as the default file handler for scripts. ** Changed in: libgnome (Ubuntu) Status: New = Confirmed -- gnome-open keeps re-running itself if set as default opening application https://bugs.launchpad.net/bugs/341389 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 271126] Re: [users-admin] changing password via users-admin doesn't change seahorse password
You just happened to choose to make your keyring password match your login password way back when it first asked Without wishing to contradict you, that's not correct -- not with recent versions of Ubuntu, at least (I'm not sure about older versions). If you don't believe me, create a new account, log on to it, and try it yourself. The login keyring is set up with that user's login password when you create the account. The automatic unlocking, incidentally, is done by libpam-gnome-keyring: This package contains a PAM module that will automatically unlock the keyrings using your login password, making gnome-keyring usage transparent without losing its security benefits. And that's the problem: once you change your login password, libpam-gnome-keyring can no longer unlock the login keyring with it, since users-admin doesn't change that password in sync with the login password. -- [users-admin] changing password via users-admin doesn't change seahorse password https://bugs.launchpad.net/bugs/271126 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 271126] Re: [users-admin] changing password via users-admin doesn't change seahorse password
I'm using 32-bit. I've just reconfirmed that the bug definitely exists on my system by creating a new user account and setting up a mail account in Evolution, which worked fine with no keyring prompts asking for a password. I then changed my password in users-admin and logged out and back in again. Evolution then complained that the default keyring was locked, and asked for the keyring password (the login password before I changed it). I'm puzzled that you didn't have this problem. Maybe it's an artifact of my system not being a fresh install of Hardy (it was originally 7.04, twice dist-upgraded)? -- [users-admin] changing password via users-admin doesn't change seahorse password https://bugs.launchpad.net/bugs/271126 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 271820] Re: gksu does not warn about programs not in root's $PATH
** Attachment added: Would you notice the period? http://launchpadlibrarian.net/17734701/gksu.png ** Visibility changed to: Public -- gksu does not warn about programs not in root's $PATH https://bugs.launchpad.net/bugs/271820 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 271820] Re: gksu does not warn about programs not in root's $PATH
** Description changed: Binary package hint: gksu The gksu prompt is identical for running programs wherever they are located. This gives rise to an easy method of privilege escalation (albeit with an element of user interaction). For example, an intruder with current user privileges could create the the folders ~/usr/sbin/, make a shell script called synaptic in that folder that installs a rootkit and launches the real synaptic, and - finally edit ~/.local/share/synaptic.desktop to change the Synaptic menu - item from gksu /usr/sbin/synaptic to gksu ./usr/sbin/synaptic. + finally edit ~/.local/share/applications/synaptic.desktop to change the + Synaptic menu item from gksu /usr/sbin/synaptic to gksu + ./usr/sbin/synaptic. Since the only change in the gksu prompt would be the addition of a single full stop, most people, I would guess, would not notice the difference (see attachment). Of course, an attacker could do this to all programs that launch with gksu, to give a larger chance of the malicious script being run sooner. Part of the script (once it successfully runs) could be to reverse the changes to the menus to reduce chance of detection. So as long as the user doesn't notice the /usr directory in their home folder (and, frankly, most users' home folders are crammed full of junk put there by various applications -- I have about 120 folders in mine), the chances are this could all go undetected. My suggestion would be to have the gksu prompt display a banner of some sort at the top of the prompt if the program being launched is not in root's $PATH (the user's $PATH wouldn't work, since an attacker with user privileges could just modify it), warning the user that the program they are elevating a non-system program. The exact wording isn't that important: the important thing is to make the prompt look different to the usual prompt, so a user who is used to seeing the normal prompt when launching synaptic would know that something's amiss. Anyone looking for an example of how this might feel might like to compare the following elevation prompts from Another Operating System: http://snurl.com/sysprog, http://snurl.com/otherprog (albeit that's based on whether the running program is digitally signed by the OS manufacturer, rather than the path. Sadly Ubuntu executables aren't digitally signed, though there is a suggestion on https://wiki.ubuntu.com/ProactiveSecurity that they might be in future). -- gksu does not warn about programs not in root's $PATH https://bugs.launchpad.net/bugs/271820 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 270994] [NEW] Context menu key doesn't work in Synaptic
Public bug reported: Binary package hint: synaptic The context menu key (between AltGr and Right Ctrl on most modern keyboards) should, when an item in a list has focus, bring up the same context menu that right-clicking on that item does. Per the Gnome HIG, Shift+F10 should have the same effect (for those with keyboard that do not have a menu key). Neither of these keys has any effect in Synaptic. Expected behavior: when a package is highlighted, pressing the menu key or shift+F10 should bring up the package context menu. Workaround: most of the items in the context menu are available in the Package main menu, accessible with Alt+P. Synaptic version: 0.61ubuntu9, in Hardy. ** Affects: synaptic (Ubuntu) Importance: Undecided Status: New -- Context menu key doesn't work in Synaptic https://bugs.launchpad.net/bugs/270994 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 17052] Re: Cannot right-click on pinned package
I can confirm as well. I'm not sure why is this wishlist. True, whilst most of the items on the normal right-click menu are available in Package menu, so it's not much of an inconvenience, surely that doesn't mean that not being able to get the context menu of a pinned package is expected behavior..? -- Cannot right-click on pinned package https://bugs.launchpad.net/bugs/17052 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 245843] Re: should be prevented from adding 'admin' as user
*** This bug is a duplicate of bug 236305 *** https://bugs.launchpad.net/bugs/236305 ** This bug has been marked a duplicate of bug 236305 Creating user with username 'admin' hoses admin group, sudo config -- should be prevented from adding 'admin' as user https://bugs.launchpad.net/bugs/245843 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 271126] [NEW] [users-admin] changing password via users-admin doesn't change seahorse password
Public bug reported: Binary package hint: gnome-system-tools When you install Ubuntu, the login keyring is created in Seahorse using the supplied login password, which is then automatically unlocked when the user logs in. However, when you change your user account password with users-admin, the login keyring is not updated. Which means that after the the user's next logged out and back in again, the next time they use an application which wants access to the keyring, they're prompted for a password when they never were before -- which would normally be no problem, except that the password the dialogue needs is their *previous* login password, which is not at all obvious. If you want the keyring to be automatically unlocked when you log in again, every time you want to change your password, you have to do it twice -- in Encryption Keyrings as well as in Users Groups. When I first came across this, it was actually about six months (during which I'd changed my password several times) by the time I first used an app which wanted access to the keyring (nm-applet); so I had to try and remember what password I used when I first installed Ubuntu -- and that only once I'd worked out that was what it wanted. Expected behaviour: When a user changes their password with users-admin, users-admin should update the login keyring. Version: Hardy, so 2.22.0-0ubuntu9; seahorse 2.22.2-0ubuntu1. (I would have thought that someone would have filed this already, but I can't find it if they have. Surely I can't be the only person who's changed their password?) ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- [users-admin] changing password via users-admin doesn't change seahorse password https://bugs.launchpad.net/bugs/271126 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 196135] Re: Timidity shouldn't depend on freepats
The fluids package that's in the repositories doesn't seem to come with a .cfg file; so I've attached one that I got from the Timidity web site and made the relevent changes to it so it works with the Ubuntu fluids package. Just dump this somewhere (e.g. /etc/trinity/) and change the source line in timidity.cfg to point to it. For anyone who hasn't done a comparison themselves, I've uploaded good old ONESTOP.MID, as rendered into an Ogg file with both Freepats and Fluid3, so you can hear the difference it makes. Freepats: http://home.btconnect.com/geoffwoolf/files/onestop_freepats.ogg Fluid3: http://home.btconnect.com/geoffwoolf/files/onestop_fluid.ogg ** Attachment added: Timidity configuration file for Fluid3 soundfont package http://launchpadlibrarian.net/13165830/fluid3.cfg -- Timidity shouldn't depend on freepats https://bugs.launchpad.net/bugs/196135 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 201593] Re: gnome-display-properties cannot put monitors beside each other, no other tool to do this available to users
Without wishing to sound obnoxious, or ungrateful for the excellent work the Bryce Harrington and others are doing in this area; is it really the case that the latest version of the most popular Linux distribution on the planet is shipping with no way to graphically enable multiple monitors (for xrandr-enabled drivers)? Surely even an applet with one large button that says Enable all monitors! which runs xrandr --auto (and maybe another button to switch between --left-of and --right-of options in case the autoconfigure picks the wrong one), as crude as it would be, would be vastly better than nothing! Not that I'm saying I disagree with the decision to get rid of displayconfig-gtk. I realise that one data point proves nothing, but the only thing I've ever had it do is trash xorg.conf, requiring a sudo dpkg-reconfigure -phigh xserver-xorg before X would work at all. Goodness knows what people uncomfortable with the command line do; presumably, go back to Windows (which has had seamless on-the-fly dual monitor configuration since Windows **98**...). NVidia users at least have a graphical configuration utility which, as I understand it, works pretty well. But ATI users like myself (not to mention Intel, SiS etc. users) are currently rather poorly served. (I realise the radeon binary drivers come with an aticonfig utility that you can use to get dual screens; I have tried it, and it was not a pleasant experience (many graphical glitches combined with frequent X crashes)). Dual screens are a pretty mainstream option these days. Considering how hard it has traditionally been to configure dual monitors on Linux, it seems a criminal shame to not take advantage of how easy it now is with Xorg 7.3 and xrandr 1.2, to finally give Ubuntu users proper, working graphical configuration of dual monitors. -- gnome-display-properties cannot put monitors beside each other, no other tool to do this available to users https://bugs.launchpad.net/bugs/201593 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 201593] Re: gnome-display-properties cannot put monitors beside each other, no other tool to do this available to users
Apologies: I retract part of my post, to the extent that I've just tried gnome-display-properties again, and this time, it *was* possible to enable both monitors (i.e. giving dual screens). Last time I tried this a week or two ago, enabling the second monitor disabled the first; so I assume the tool was updated since then (presumably by Bryce Harrington -- thanks!). It still put them the wrong way round, and there being no way to specify which way round they should go graphically, I still had to use the command line tool to specify --left-of. I remain hopeful that despite what Bryce wrote here last month, a simple drop-down menu to specify 'left' or 'right' might be slipped in before Hardy gets released...? -- gnome-display-properties cannot put monitors beside each other, no other tool to do this available to users https://bugs.launchpad.net/bugs/201593 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
