Public bug reported:
Fails during update, progress bar never finishes on Icon.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: uuid-runtime 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubunt
Public bug reported:
Fails during update, progress bar never finishes on Icon.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: uuid-runtime 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubunt
Can't seem to get it to reproduce now that I've disabled and re-enabled
low graphics mode for the second screen shot. So I guess we can close
this for now, sorry for the hassel. If I can get it to happen again
I'll re-open with a screen shot.
** Description changed:
While in low graphics mod
Public bug reported:
While in low graphics mode, various icons in the status bar show broken
while. If low graphics isn't enabled, the icons show up correctly.
See screenshots for more information. Theme (gtk and icon) doesn't seem
to make a difference. For the purposes of this report, I used
Same issue here on a Dell Latitude E5470.
OS: Ubuntu 16.10
Kernel: 4.8.0-22-generic
CPU: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
GPU: Intel Corporation HD Graphics 520 (rev 07)
Xorg (package version): 1:7.7+13ubuntu4
Also it's very intermittent, hard to forcefully reproduce. I was doing a
test
This is my first bug filed in Launch pad, wasn't sure how to set this
bug to Trusty as the release.
** Package changed: unity (Ubuntu) => unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299932
T
Public bug reported:
When locking the screen from Unity, the monitor doesn't go into standby,
instead the Unity login screen (now also the lock screen) appears.
Upon unlocking, the screen will relock itself usually with in about 15
seconds after unlocking with the monitor now in powersave mode.
S
Same issue here; Nautilus 3.8.2 .. Happens any time there is an image
file that is 0 bytes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203349
Title:
nautilus crashed with SIGSEGV in _gdk_pixbuf_
Experiencing the same issue:
***MEMORY-ERROR***: evolution[25331]: GSlice: assertion failed:
sinfo->n_allocated > 0
Ubuntu 13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169694
Title:
evolut
I have the same issue on a windows version
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.15) Gecko/20110303
Thunderbird/3.1.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701090
Title:
warcry glad it work for you it is a pain but least we've got round it.
Given we've changed the NVidia closed source drivers I'm not sure it's
really something ubuntu can fix, aside from providing older drivers by
default.
I can't find a definitive answer on the NVidia site about whether the
260.xx
I worked round the problem with this approach:
http://ubuntuforums.org/showpost.php?p=9964095&postcount=21
seems to be the 260 driver that's included in Maverick not working with
my hardware; 8300GS
--
nvidia driver does not work in maverick on GeForce 8300 GS
https://bugs.launchpad.net/bugs/65
Got mine working again, these are the packages I have installed:
nvidia-173-modaliases 173.14.28-0ubuntu1 Modaliases for the NVIDIA binary
X.Org driver
nvidia-96-modaliases 96.43.18-0ubuntu1 Modaliases for the NVIDIA binary
X.Org driver
nvidia-common 0.2.24
/Same for me, Dell Latitude with GeForce 8300GS installed. Drivers that
come with 10.10/Maverick give me a blank screen instead of the logon
(can hear the tom-toms so it's worked though).
Reverted to 256.53 using the link/info above and it's working ok.
--
Beta 10.10 Nvidia update broke Sony Va
** Attachment added: "The wrong value as shown in Power Statistics page."
http://launchpadlibrarian.net/38583470/Screenshot.png
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38583471/Dependencies.txt
** Attachment added: "DevkitPower.txt"
http://launchpadlibraria
Public bug reported:
Binary package hint: gnome-power-manager
Summary According to the battery specification
(http://h18000.www1.hp.com/products/quickspecs/12152_na/12152_na.HTML),
my battery with model number EH767AA has a Watt-hour capacity of 55Wh.
The battery-full-design value as show in gnom
I had the same thing, fixed it by getting rid of the fast user switcher
applet (the Ubuntu one that has the IM status as an icon) and using the
default gnome user applet (the one that has you're .face file as the
icon).
--
The nm-applet icon is missing or the sound icon is duplicated and the seco
I've got a very similar problem, same error reported on boot "...one or
more of the mounts listed in /etc/fstab cannot yet be mounted..." with
the effected drives being my two LVM's which are NOT encrypted.
It all boots up and works ok just get the 'fstab' text (as per post #6)
scrolling in a litt
I've just tested on a Karmic beta live CD and the volume on the mic is
low but can easily be turned up in padevchooser. Once the mic volume
was turned up it seems to work fine, I could record from the mic using
the sound recorder, playback worked out of the box.
Can probably leave this issue for
"1) I had a driver problem fixed but updating ALSA to >= 1.0.19
(currently got 1.0.21(a) installed). This for my mic working"
should read
1) I had a driver problem fixed by updating ALSA to >= 1.0.19 (currently
got 1.0.21(a) installed). This got my mic working outside PA.
--
Recording does not
I've had the same issue on 9.04 with my 1500 Vostro. I worked round it
by disabling the HAL detect module in PulseAudio (default.pa) and only
enabling an ALSA sink. ie. I didn't let PA 'know' about my built in mic.
Also updated to the latest ALSA drivers, utils, libs, plugins and tools
by downloa
Little more info. Not sure what happens with Compiz but if the fact
that the Guest account had Compiz disabled (because of blacklisted intel
graphics card) then maybe that could account for the Compiz stopping on
session 'A'.
Also, when logging out of Guest account I've had an unresponsive blank
Hi.
I've got the same issue; blank screen when trying to switch user or
start another x session.
I updated my 9.04 install from the PPA listed above and user switching
now works, thanks for the fix Bryce.
However there are other issues related to this though I'm not sure if
they're a totally dif
23 matches
Mail list logo