marked invalid. re-open if necessary.
** Changed in: compiz-plugins-main (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1355196
Title:
unity crashes
Chris seems to have correctly identified the issue.
I tried reverting the xserver-xorg-video-intel to previous versions, but it had
no affect.
I rebooted into an older kernel and i can still use compiz/unity.
3.16.0-6-generic : works
3.16.0-7-generic : fails
3.16.0-8-generic: fails
**
$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
OpenGL version string: 2.1 Mesa 10.2.5
Not software rendered:yes
Not blacklisted: yes
GLX fbconfig: yes
** Attachment added: guest's home dir during failed login (log files in
.cache)
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176600/+files/guest-home.tar.gz
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
** Attachment added: /var/log/kern.log messages from guest login
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176601/+files/guest-kern.log
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
** Attachment added: /var/log/Xorg.0.log from guest login
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176602/+files/guest-Xorg.0.log
** Changed in: unity (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
This reproduces in the guest login also.
** Changed in: unity (Ubuntu)
Status: New = Confirmed
** Changed in: unity (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching
Public bug reported:
Recent upgrade and reboot/re-login left me with a generally unusable
compiz/unity.
On login, the desktop icons move back and forth several times, I believe this
correlates with ~/.xesssion-errors 'unity main process ended' messages like:
upstart: gnome-keyring main process
For what its worth, this is an older thinkpad (T400). It has older
intel graphics chipset. I'm attaching xorg.0.log for more information.
** Attachment added: xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4174472/+files/Xorg.0.log
--
You received
it appears this was fixed under bug 1238111.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1233205
Title:
maximize then unmaximize of gnome-terminal
** Description changed:
This sounds a lot like bug 772972, but I'm seeing it in saucy.
If you maximize a gnome-temrinal and then un-maximize it, it will shrink
by a full column and row.
* run 'gnome-terminal'
* click the maximize button (or keybinding 'maximize')
* click the
Public bug reported:
Long bug title, but I see some issues with dialog windows and unity (or
compiz) and multiple desktops.
I have 6 different desktops and typically leave a chromium-browser
running in one. I'll have full screen windows in the others, and
To reproduce my initial problem:
*
Public bug reported:
This sounds a lot like bug 772972, but I'm seeing it in saucy.
If you maximize a gnome-temrinal and then un-maximize it, it will shrink
by a full column and row.
* run 'gnome-terminal'
* click the maximize button (or keybinding 'maximize')
* click the unmaximize button
Public bug reported:
Sometime in saucy my battery icon started showing '(estimating...)' for
the 'time' in the menu bar.
This could be because I:
a.) am plugged into power
b.) have used the thinkpad 'tp-smapi-dkms' packages to control my battery,
telling it to not charge even though its plugged
so its probably related to the fact that I've explicitly told the battery not
to charge while plugged in.
Thats accomplished by:
stop=80
start=40
bat_d=/sys/devices/platform/smapi/BAT0
sudo sh -c echo $stop $bat_d/stop_charge_thresh echo $start
$bat_d/start_charge_thresh
More info at
16 matches
Mail list logo
