[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
Does the fact that I see this behavior in *Trusty* (see comment [url=https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/comments/33]33[/url] mean that I'm experiencing this same bug, or is it another issue altogether for which I should open a separate bug? Please notice that (as stated in comment 33) I've actually purged all samba packages from this system, the only things left behind are some samba libraries, and yet the gvfsd-dnssd process would randomly start for no reason that I can thin kof and load the CPU to the max. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1409032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
I think I may have the same issue in Trusty, possibly even worse: the gvfsd-smb process would randomly start and totally max out the CPU for no apparent reason - the thing is, not only I don't use samba at all, I have actually *purged* all samba packages from this system. I really can't see how this process, which should be spawned by samba, should even start at all (let alone load the CPU to its max) when samba isn't even installed any more in my system. This being an old laptop which easily overheats, after getting nowhere trying to figure out why gvfsd-smb does this, I've resolved to remove the executable bit from gvfsd-smb and gvfsd-dnssd (which also starts for no apparent reason) and finally got rid of this big issue. But nonetheless I believe that such an annoying (and potentially harmful) long-standing bug should be properly investigated and fixed once and for all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550722] [NEW] VirtualBox notification at boot in Ubuntu Wily 15.10
Public bug reported: In Ubuntu Wily 15.10, the following notification message is displayed at *every system boot* once the desktop graphical environment (MATE) is started: "VBoxClient: the VirtualBox kernel service is not running. Exiting." To be precise, this is actually the exact same issue I also had in Vivid. Ubuntu 15.10 virtualbox 5.0.14-dfsg-0ubuntu1.15.10.1 virtualbox-dkms 5.0.14-dfsg-0ubuntu1.15.10.1 virtualbox-guest-additions-iso 5.0.14-1~ubuntu1.15.10.1 virtualbox-guest-utils 5.0.14-dfsg-0ubuntu1.15.10.1 virtualbox-guest-x11 5.0.14-dfsg-0ubuntu1.15.10.1 virtualbox-qt5.0.14-dfsg-0ubuntu1.15.10.1 What should happen: there should be no notification from virtualbox if there's actually nothing to notify, and the virtualbox application isn't even running. What happens instead: at every reboot a notification from virtualbox is displayed. ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: virtualbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550722 Title: VirtualBox notification at boot in Ubuntu Wily 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1550722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550718] [NEW] VLC fonts and GUI style can't be set with QT in Wily
Public bug reported: In Ubuntu Wily 15.10, the GUI style and fonts for VLC can't be set using the qt4-qtconfig tool: unlike the previous versions installed in Vivid, in Wily the applications VLC 2.2.1-3 and qt4-qtconfig 4:4.8.6 don't work together. VLC in fact doesn't respond to any change made using the QT configuration tool. Ubuntu 15.10 vlc 2.2.1-3 qt4-qtconfig4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 What should happen: GUI style and custom fonts settings should be applied in VLC using the qt4-qtconfig QT configuration tool. What happens instead: settings changed using the qt4-qtconfig QT configuration tool have no visible effect at all in VLC. ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: qt4 vlc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550718 Title: VLC fonts and GUI style can't be set with QT in Wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1550718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538104] [NEW] traps: mate-notification message in logs
Public bug reported: I'm always seeing this message after boot in Ubuntu-Mate 15.04 in syslog, kern.log and dmesg and also with journactl --boot: traps: mate-notificati[1409] trap int3 ip:7f67f920ed00 sp:7ffd6097e640 error:0 what does this mean? Ubuntu release and package version: Ubuntu 15.04 mate-desktop 1.8.2+dfsg1-2 mate-desktop-common 1.8.2+dfsg1-2 mate-desktop-environment-core1.8.0+9 Kernel: 3.19.0-47-generic x86_64 (64 bit gcc: 4.9.2) Desktop: MATE 1.8.2 (Gtk 3.14.13) dm: lightdm Distro: Ubuntu 15.04 vivid ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538104 Title: traps: mate-notification message in logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1538104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538086] [NEW] Seahorse has no option to export/import passwords
Public bug reported: Seahorse 3.15.90-0ubuntu1 in Ubuntu15.04 still has no option for exporting and importing stored passwords ( see: bug https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/550101 and comment https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/550101/comments/19 ) : since it can manage importing and exporting of gpg keys, and it also has this additional ability to store encrypted passwords, it would make sense to also manage these stored passwords as well. That would greatly add to its usability as a password manager as well, in addition to being a gpg key manager. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538086 Title: Seahorse has no option to export/import passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1538086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550101] Re: Export of keys and keyrings is not available
This issue is still present in Ubuntu 15.10: Seahorse to date still has no option to export/import stored passwords. This kinda hinders its abilities as a password manager: even if it's probably meant to be mainly a gpg key management interface, it also has this ability to store passwords, so not being able to export/import those as well detracts from its usability forcing users to seek alternative solutions. Given that there has been no activity in this bug since 2014 (see comment above), should eventually a new bug be opened tagging current and future releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550101 Title: Export of keys and keyrings is not available To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/550101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
That was (probably) more or less a given, this is clearly an ATI/fglrx issue. What I don't understand is why is considered somehow acceptable to suffer such an issue, or why the recommended "fix" (?) would be to get rid of the fglrx driver altogether. ATI support for Linux may be considerably worse than Nvidia (as recognized by many people in the know), but if the package exists in the Ubuntu repository it should work without rendering the virtual consoles useless, and this issue shouldn't slip all the way from 14.04 to 15.10. That >removing fglrx drivers is some sort of workaround, but presumably people that did install fglrx in the first place >want fglrx for some reason is the appropriate line of reasoning: the official package exists and should be installable without breaking anything major such as the virtual consoles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
>The "who" command verified to me all my tty consoles are fully functional, only their displays are blacked out. We know that already, the issue is that they are not really usable if blacked out: we have a monitor/display for a reason. We also know that getting rid of the fglrx driver solves the issue right away, unfortunately the fglrx driver also exists for a reason, which would be that the open source driver can't do the same things: at least in my experience, I'm stuck with very basic graphics, I can't set the monitor brightness, I can't use hardware acceleration or use Compiz effects. These are real drawbacks, if I have to do without this stuff, I may as well do without the ATI video card and use the integrated graphics on the motherboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
This is also happening in Ubuntu Trusty 14.04.3 LTS : right after installing fglrx-updates and fglrx-amdcccle-updates the virtual consoles become unusable, i.e. totally blank. Again, as bad as the AMD support for Linux may be, as a matter of fact the proprietary driver is (unfortunately) still better then its open source counterpart: display quality is noticeably better, screen adjustments are way easier and more fine tunable than messing around with xrandr, composite window managers don't work properly or don't work at all with the open source driver. Much as I would like to do without the proprietary AMD driver, I need to use it to have my hardware working as I want, so please fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
In reply to comment https://bugs.launchpad.net/ubuntu/+source/fglrx- installer-updates/+bug/1470862/comments/5 I recommend you to get rid of fglrx. Open source drivers for AMD work today like a charm. I beg to differ: much as I would really like to get rid of any non-free components, without the fglrx driver *I can't even set the display brightness* let alone do more refined tweaks, furthermore it is needed for a composite window manager (such as Compiz) to work. I'm not saying that open source video drivers don't work, I just can't do all the things I want with them -besides, I know for a fact that virtual consoles didn't disappear in previous Ubuntu releases when using the fglrx driver, so it's clearly a regression that should be fixed ASAP. I can't tell if the problem is the latest fglrx driver itself or some grub setting or whatever, anyways I've tried some suggested workaround such as turning off the graphical terminal or changing the screen resolution in /etc/default/grub and unfortunately it didn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
I'm affected by this bug too in Ubuntu Mate 15.04 amd64, after installing fglrx-core 2:15.200-0ubuntu4 , fglrx 2:15.200-0ubuntu4 and fglrx-amdcccle 2:15.200-0ubuntu4 the six virtual consoles are blank, only Ctrl+Alt+F7 works to get back to the graphical environment. Removing the fglrx packages brings back the consoles. In past Ubuntu releases (Lucid and Precise) I did not have this bug, although the fglrx driver in that case had been manually installed starting from the installer downloaded from the AMD site rather than directly installing the fglrx packages from the official Ubuntu repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424119] Re: Edit Connections...now insensitive by default in network manager's menu
I still had the bug with network-manager-gnome 0.9.4.1-0ubuntu2.5 in Mint13 (based on Ubuntu 12.04 LTS), I've had to revert to version 0.9.4.1-0ubuntu2.1 to get rid of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424119 Title: Edit Connections...now insensitive by default in network manager's menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1424119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue
I still disagree: being greeted with an error message right after finishing the installation of a new OS isn't exactly the right way to start, isn't it? Cosmetic or not, apart from seasoned users who may have seen worse, this ain't going to make a great impression on newcomers to Ubuntu- if anything, it will make it appear a bit like windows, although in the end they might find this reassuring... There also may be more to it, although frankly I'm not sure at this point if it is directly related or not: as I've said above in comment https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247/comments/68 after installing Lubuntu 14.04 on a new SSD I wasn't actually able to boot the installed system, I had indeed to create a separate dedicated /boot partition or else it would never boot. That I wouldn't call cosmetic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: [Grubenv] error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue
That's not the way to do it: it may work, but this is an Ubuntu (major) bug and should be solved without adding packages from the Debian package repositories. Also, it is worth reiterating that an LTS release such as Ubuntu 14.04 has to be fixed, period. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: [Grubenv] error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue
Seriously, this isn't going to be backported to 14.04 ? Ubuntu 14.04 is supported until 2019,and this is a major bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: [Grubenv] error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
Sorry,the bug I've linked is about grub either breaking after an update to 14.04 (for some people) or not working right after a clean install of 14.04 (for some other folks,including me):I somehow assumed that it could be related to this one,although the error message is different. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
On 11/01/2014 06:20 AM, Teo wrote: Which confirms there's a bug somewhere. No, it does not. Installing grub to the wrong place because you manually chose it is not a bug. Installing grub to /dev/sda by default when your computer actually boots from another drive is also not a bug, because unfortunately, there simply is no way to detect which drive the computer boots from due to the limitations of the pc bios. If grub outright failed to install, then there *may* be a bug. The installer automatically files a bug report when this happens so it can be investigated. Did you have a look at this other bug https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247 ? There has to be something wrong in Ubuntu 14.04 concerning grub,because in some fresh installations,after everything has finished normally and the OS has been apparently installed without errors,then the system simply won't boot at all,period. The workaround has been installing grub to a dedicated boot partition,something I wouldn't call a normal installation procedure:I've never had to do that with any other Linux system so far,including previous Ubuntu releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046563] Re: update-manager never appears on lubuntu precise trusty
I think we might be meant to manually launch the update manager as the first thing upon loading? I really don't think so,in other distros I've used (including older Ubuntu releases) the update manager constantly pops up on its own right after booting,which doesn't happen in Lubuntu 14. The only way to see it appear (short of launching it manually) is to not apply all updates and then click remind me later-but then,after applying the remaining updates,it's gone until you re-launch it manually. That doesn't look to me at all as the expected/correct behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046563 Title: update-manager never appears on lubuntu precise trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1046563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
