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
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
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
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
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?
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
) :
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
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
>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
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
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
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
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.
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
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
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:
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
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
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
19 matches
Mail list logo
