It looks weird because I accidentally hit PrtSc without Alt, darkening
the screen, then was too lazy to close the dialog (keeping the screen
darkened) before hitting Alt-PrtSc again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Here's a screenshot of the same thing in Software Updater
** Attachment added: "Screenshot of Software Updater"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1547119/+attachment/4660019/+files/Screenshot%20from%202016-05-10%2013-46-38.png
--
You received this bug notification
I'm getting the same thing after installing Ubuntu 16.04. Usually, this
appears after opening my laptop lid from suspend, and it only seems to
happen on one particular Wi-Fi network.
Going to a terminal and typing `killall nm-applet` then `setsid nm-
applet` seems to reset the icon back to normal.
@Adam Niedling - I agree that even though it's slightly less annoying
than before, the new 16.04 behavior is still not very good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170647
Title:
After m
6 years later, and this is still a problem.
Besides wrestool, might want to take a look at the md5sum command that
creates an icon based on the file md5sum when there's no icon embedded -
this also creates a lot of disk activity and cached RAM. I hacked up a
solution with changing a line to 'HUE=$
I also get 'File descriptor 50 (/dev/pts/6) leaked on vgs invocation. Parent
PID 14069: /usr/sbin/grub-probe
' whenever apt-get updates grub's configuration file... which is several times
when you're removing multiple old kernels...
I would've thought this would be fixed by now.
--
You receive
ubuntu@ubuntu:~$ sudo grub-probe -t fs -vvv -d /dev/sdc1
grub-probe: info: cannot open `/boot/grub/device.map': No such file or
directory.
grub-probe: info: cannot stat `/dev/sdc1': No such file or directory.
grub-probe: info: /dev/sdc1 is not present.
grub-probe: info: Looking for /dev/sdc1.
grub
Here, I took a screenshot with extra information. Note that is a
completely different computer, and a Ubuntu 14.10 64-bit live USB.
** Attachment added: "Screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1407017/+attachment/4296750/+files/Screenshot.png
--
You rec
I have a Dell Latitude 2120. On boot, /sys/class/leds/dell::lid does not
exist because the dell_led module isn't loaded. It does after running
'sudo modprobe dell_led'. However, without doing anything else:
hitechcomputergeek@hitechcomputergeek-Latitude-2120:~$ modinfo de
This happens for me with a Transcend USB3.0 1TB drive. (I checked, and
it has the latest firmware, too.) I agree with Romano Giannetti that
this should be marked Critical - I can still unmount my main btrfs
partition first, which should sync any writes to the disk, but I really
don't know how bad i
Not fixed for me on Wily, either. Also, I noticed that if you already
have a Nautilus window open on another workspace (even not for a drive),
unlike most other apps (where it switches to the workspace with that app
open and brings the window to the foreground), Nautilus will instead
open a new win
For me, this usually happens right as a video I was playing ends. when
the interface returns to the empty VLC logo. The only way to get rid of
it seems to be to close and re-open VLC. Also, not sure if this is
related, sometimes when I double-click a file in Nautilus and it opens
VLC, VLC will open
More like a fraction of a second actually. This especially happens if I
double-click a file and then immediately double-click another in
Nautilus, so that VLC is supposed to switch to the new file instead. (I
may just be clicking things too fast, but this worked fine in 15.04.)
However, occasionall
Wait a minute, unlike the OP I haven't disabled the global menu... let
me get a screenshot...
** Attachment added: "Screenshot from 2015-11-04 19-56-34.png"
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1510624/+attachment/4513124/+files/Screenshot%20from%202015-11-04%2019-56-34.png
--
*facepalm*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170647
Title:
After minimizing a Nautilus window of another partition or external
media or Trash folder, clicking on the "Files" icon on t
[angry rant]
I'm really getting sick of people fighting about whether this is a bug or not
(despite there being no other application that I've seen that has this
behavior), and changing tags, and submitting patches, and rejecting patches,
and there being like 20 duplicate bugs of this and over 3
I'm getting this too. When I tried to nano my ~/bashrc file (just as me,
not as root), the first two times it segfaulted. The third (and any
later) times, now it displays "Couldn't determine hostname for lock
file: File name too long" for ANY file I try to open or create. Upgraded
from Ubuntu 15.04
I forgot to mention, now I get "Couldn't determine hostname for lock
file: File name too long" when I try to run nano as both me AND root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509081
Title:
*** This bug is a duplicate of bug 815996 ***
https://bugs.launchpad.net/bugs/815996
I don't think this is a duplicate. The other bug appears to be about
switching workspaces THEMSELVES, while this is moving WINDOWS between
them by dragging. Switching workspaces has never caused me any problem
Public bug reported:
Ubiquity installer first said that the bootloader (which was set to
install to a USB flash drive, /dev/sdc) was unable to install, then
immediately after I closed the error dialog, the installer crashed.
This happened twice in a row, on separate boots.
Version: Ubuntu 14.10
** Attachment added: "Screenshot of error message"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1407017/+attachment/4291373/+files/installer2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I had picked "Something Else" when I was in the installer. I had taken a
screenshot, but originally decided not to upload it; I attached it. Note
the first time I tried the install, I picked /dev/sdc for bootloader
installation, but I took the screenshot the second time, when I tried
picking /dev/s
I had picked "Something Else" when I was in the installer. I had taken a
screenshot, but originally decided not to upload it; I attached it. Note
the first time I tried the install, I picked /dev/sdc for bootloader
installation, but I took the screenshot the second time, when I tried
picking /dev/s
23 matches
Mail list logo
