[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Latest Wily: DISTRIB_DESCRIPTION="Ubuntu 15.10" Linux Lenovo2 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA c

[Touch-packages] [Bug 1509740] [NEW] Could not apply the stored configuration for monitors

Public bug reported: Message on booting up. See attached. Came up in 1920x1080 expected 1366x768 Screen flashed a couple times, once in 1366x768, then back to max resolution hard to read on this monitor. Systems settings to get desired resolution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Pa

[Touch-packages] [Bug 1509740] Re: Could not apply the stored configuration for monitors

This bug persisted for two weeks. Installed and updated Xenial problem no longer occurs. Much safer for me to update Ubuntu rather than risk a bios update - a failed bios update turns the pc into junk. Thanks for looking at the bug. -- You received this bug notification because you are a membe

[Touch-packages] [Bug 1484226] Re: Wily after log in wallpaper hashed

*** This bug is a duplicate of bug 1404247 *** https://bugs.launchpad.net/bugs/1404247 Finally a workaround was posted: #sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf #Add the following lines Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" E

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Finally a workaround was posted on Launchpad - I've been battling this bug for 11 months: #sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf #Add the following lines Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection #reboot -- You receive

[Touch-packages] [Bug 1501028] [NEW] unity-panel-service crashed with SIGSEGV in ffi_call_unix64()

Public bug reported: Wily Beta 2 Gedit a text file got this error ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: unity-services 7.3.2+15.10.20150921-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/app

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Wily Werewolf here, updated as of 14 may, boots normally, no Hashing. Reboot to 15.04, screen Hashed as usual. Reboot to Wily Werewolf, boots normally again, no Hashing. Wonder what next updates will do -- You received this bug notification because you are a member of Ubuntu Touch seeded p

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

As of 17 May Wily update, xserver was updated Now, hashing much harder to get rid of by multiple "set wallpaper". How do I tell if the bug fix is in Wily? If so, it doesn't work. If not, when can I try the fix? Thanks. -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Bios update is in 1404247 - if it screws up I've got a dead computer. 1410 and before run just fine. November and before 1504 ran fine. Win7 just fine. (Well, pretty slow it's Microsoft) 1504 December and on to now pretty bad. I have to "set wallpaper" multiple times. At the moment, Wily muc

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

gsettings set org.gnome.desktop.background picture-uri 'file:home/jerry/Pictures/Shark_Island.jpg' re-does the wallpaper and can clean up the hashing. What all does "gsettings" use? Likely xserver -- You received this bug notification because you are a member of Ubuntu Touch seeded pac

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Shotwell display badly hashed. Image Viewer display just fine. Both on the screen at the same time in the attached screenshot. How do I get the display routine used by Image Viewer to be used by Shotwell and Lightdm? Note, part of screen behind the images shows badly hashed unreadable desktop.

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Wily O.K. for a couple weeks and I had my hpes up. Then got dread update: xserver intel update Now wallpeper usually boots horizontally striped hashed, sometimes boots wallpaper O.K. I don't know how to down level xserver intel? Wallpaper can be fixed by alternately doing the following once or

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Wily as of DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)" Linux Lenovo2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model na

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Opened a bug for gsettings failure described in comment #26: gsettings fails to set wallpaper 1490543 Gsettings fails on both the Lenovo M58p with the hashing problem Gsettings also fails on Acer 5253 laptop which does not have the hashing problem In both pc's Settings Appearance Wallpapers Pic

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Update complete Wily as of display. Appearances Background all pictures horizontally hashed, both the ubuntu supplied ones and my jpg's. Wallpaper horribly hashed and will not recover even with multiple wallpaper settings. which used to clear things up until the changes of last week. Files Pictu

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Wily getting worse and worse. Much screen text hashed unreadable. A couple weeks ago it was just Wallpaper. Do note, Files Pictures select jpg displays jpg just fine. Settings Appearance all hashed. See attached screenshot. Do note with hashed unreadable text as in gedit, selecting screenshot

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Thanks for looking at the bug. I switch between Mily looking for bugs, and LTS when I can't get something done with Mily because I can't read the screen. I might try another kernel from kernel-ppa/mainline. I don't know how to downlevel X to say, whatever it was in November 2014 when everything

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Kernel: linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_amd64.deb works fine installed into Wily. I think it's one of the last Utopic kernels So my drill is, update or install latest Wily, verify screen display is all screwed up, Then install a kernel that will work. I'm not a d

[Touch-packages] [Bug 1420554] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers looping, abandoned

Wily apt-get update, apt-get dist-upgrade Sept 11, 2015 rebooted got this bug DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)" Linux Aspire-5253 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:43:10 UTC 2015 x86_64 x86_64 x86

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Comment #36, this is a desk top so the display is hooked to the VGA port. I think there's only one display port on this Lenovo M58p. Interesting, boot with Wily kernel, Background Wallpaper hashed Settings Appearance Wallpapers thumbnails hashed Files Pictures displays same jpg fine command lin

[Touch-packages] [Bug 1691599] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: Was installing google-chrome and got this error at the same time I don't know if it is related. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: gconf2-common 3.2.6-3ubuntu7 P

[Touch-packages] [Bug 1424074] [NEW] Vivid Unity Wallpaper horizontally hashed

Public bug reported: Wallpaper still hashed on this Lenovo M58P DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)" Linux Lenovo2 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Testing vervid I do updates most days and installs every couple weeks. Typically there are a whole pile of packages (!) so us users don't install package by package so we can't tell which caused the trouble. I reported the bug on Dec. 19 and the bug persists on every update and every couple week

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Downloaded today's vivid 32 bit, booted live environment, systems settings appearance, set wallpaper selected ubuntu skyscraper image all hashed up. See attachment. Doesn't seem to make any difference, 32 bit or 64 bit both broken. ** Attachment added: "wallpaper hashed vivd 32l bit .iso"

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Comment #7, where is the update history found? Likely hundreds of updates in December. This install is a couple days old, still has the problem. What packages are involved in "Set Wallpaper"? Any way to put "Set Wallpaper" back to early December? All my vivid iso's are now in February. -- You

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Beta 2 Vivid hashed wallpaper problem on every single boot. Updated as of just now, amd64. I did subscribe to bug in comment #15 I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

I looked at the Lenovo support site. The BIOS upgrade is for Win7 64 so I'll have to boot that ( if Ubuntu Grub hasn't screwed up the Win 7 bootloader ) and see if the download and exe will work. Of course if a BIOS update fails I've got a dead computer. -- You received this bug notification b

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Still present on every boot. See attachment. DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)" Linux Lenovo2 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 04:35:32 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux model name : Intel(R) Core(TM)2

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

As of 10 September, the amd64 daily build hasn't been built since 5 September and is still at the 3.16.0-12 level. The .iso boots to desktop as usual. No compiz/unity. >From command line do apt-get update and then apt-get dist-upgrade, reboot at >3.16.0-14 whereupon compiz/unity work. BTW, 3.17.

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

As of 11 September, the daily(?)-live current amd64 .iso is still at 5 September, 3.16.0-12, boots to desktop no compiz/unity. Daily-live pending amd64 was at 10 3.16.0-14, boots to compiz/unity fine. Installed fine (for a develompment image). I haven't heard that there was any change in the Int

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

daily-live current now dated 11 September. Zsync vs. yesterday's daily-live pending updated said 82% complete. .iso amd64 booted normally, unity panels O.K. kernel 3.16.0-14. First daily-live current that booted O.K. since July. So as of today, this bug did not occur. -- You received this b

[Touch-packages] [Bug 1370274] [NEW] utopic 3.16.0-14 internal error just when unity started

Public bug reported: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.10 DISTRIB_CODENAME=utopic DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)" Linux Aspire1 3.17.0-031700rc4-generic #201409071935 SMP Sun Sep 7 23:36:45 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -rw--- 1 root root 638675

[Touch-packages] [Bug 1370274] Re: utopic 3.16.0-14 internal error just when unity started

Updated the 3.16.0-14 booted O.K. four times. Installed rc5. Booted O.K. At grub menu, Advanced options, did e then F10 enter on rc5 booted to command line. ? Anyway, bug as originated has not recurred so assumed fixed by the update. -- You received this bug notification because you are a me

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Tried kernel 4-RC2 DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)" Linux Lenovo2 4.0.0-04rc2-generic #201503031836 SMP Tue Mar 3 18:37:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name : Intel(R) Core(TM

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Comment #11 found earlier vivid wallpaper works fine. (as does 14.10, 14.04, ...) Nov. 10 vivid .iso fresh install on another partition. Boots with wallpaper O.K. every time. Vivid as of mid December updated/installed wallpaper screwed up on every boot. This is a vivid apt-get update, apt-get di

[Touch-packages] [Bug 1406802] Re: Vivid Unity Wallpaper horizontally hashed

Yesterday installed Nov 11 Vivid .iso in another partition. Wallpaper works fine. As of mid December to present, every boot wallpaper screwed up on Lenovo M58p Files > Pictures > select jpg > set as wallpaper a couple times get correct wallpaper display. Reboot, all screwed up again. What's di

[Touch-packages] [Bug 1404247] [NEW] Vivid Wallpaper hashed

Public bug reported: After update this week wallpaper hashed. See attachment. Settings Appearance change wallpaper to a different wallpaper O.K., then back to original restores proper image. Reboot, wallpaper hashed again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubun

[Touch-packages] [Bug 1405867] [NEW] Settings > Appearance > Wallpaper does not change wallpaper

Public bug reported: Vivid update in the last week selecting new wallpaper does not work unitil reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tm

[Touch-packages] [Bug 1406802] [NEW] Vivid Unity Wallpaper horizontally hashed

Public bug reported: Standard wallpaper selection distorted badly cut and displaced sideways. See screenshot. Lenovo Desktop Dual processor: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00

[Touch-packages] [Bug 1406802] Re: Vivid Unity Wallpaper horizontally hashed

1 January 2015 isync'd today's vivid 64 image Booted the .iso image. 1. Wallpaper distored with vertical bars displayed which are not in the .iso 2. Selecting a new wallpaper does not take effect. Used to be, selecit it, and it came up. Now, shows on the little drop down window but does not

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

Jan 4 vivid 64 .iso still same problem, wallpaper vertical bars and hashed. Rebooted latest update vivid. Monitor is 1920x1080., vertical bar background. Internet windows and terminal windows fine. Tried 1360x768. Wallpaper Vertical bars. Tried 1280x720. Vertical bars. Tried 1024x768. Wall

[Touch-packages] [Bug 1406802] Re: Vivid Unity Wallpaper horizontally hashed

Vivid linux image 3.18.0-8 same problem. Systems Settings > Displays try several different screen resolutions and normal wallpaper display sometimes appears, to be trashed on next reboot. Note, bug/1405867 also still present, Systems Settings > Appearance > Wallpapers > select does not take effec

[Touch-packages] [Bug 1418745] [NEW] signon-ui crashed with SIGSEGV

Public bug reported: Internal error on boot up. Had already been updated today Feb 5, 2015. DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)" Linux Lenovo2 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 04:35:32 UTC 2015 x86_64 x86_64 x86_6

[Touch-packages] [Bug 1418745] Re: signon-ui crashed with SIGSEGV

How do I do an amd64-retrace? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1418745 Title: signon-ui crashed with SIGSEGV Status in signon-ui package in Ubuntu: New

[Touch-packages] [Bug 1484226] [NEW] Wily after log in wallpaper hashed

Public bug reported: DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)" Linux Lenovo2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name : Intel(R) Core(TM)2 Duo

[Touch-packages] [Bug 1484083] Re: Don't work autologin after update lightdm

This is Ubuntu Unity which had the autologin failure in spite of install specifying autologin and settings autologin as well. As in Post #11 now fixed, just commented out the line. Problem occurred this week with fresh install of Wily .iso daily build. Also occurred on my laptop with just Wily

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

That site looks like a fresh install to today's xenial 64. I've been running an update xenial now at 4.5 RC1; I'll do a fresh install and see what happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https

[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed

I tested http://cdimage.ubuntu.com/daily-live/current/ Wallpaper badly garbled. Images from ubuntu O.K., but any text sent by ubuntu badly garbled unreadable. Fix in comment #41 works fine. Do note, 14.04 LTS had been running fine until 1/29 update screwed up network, so I re-installed 14.04

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

Whoopsie, got another crash after the update in comment #14 in bug # 1380278 which on the surface looks like comment #12 in Bug # 1380278 .. So whatever may be in: "This bug was fixed in the package unity-settings-daemon - 14.04.0+14.10.20141014-0ubuntu1" after shutdown, boot I still got ano

[Touch-packages] [Bug 1380774] Re: debian-installer does not find kernel

As a tester I have a pile of partitions with lubuntu, ubuntu various levels, windows7, plus experimenting with Mate, debian lxde and Google 3.12 on built in hard drive and external USB solid state drive. I set up my partitions for testing the way I want with Gparted. Manual install of Lubuntu 201

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

vivid .iso boots to black screen. Ctrl-Alt-F1 sign in, ls /var/crash _usr_bin_compiz.1000.crash sudo service lightdm restart was able to install. Booted after install, got intermittently flashing wallpaper. Ctrl-Alt-F1 sign in ls /var/crash _usr_bin_compiz.1000.crash up and running. Tried a su

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

Thanks for looking at the bug. Following your instructions, got this: jerry@jerry-AOD255E:~$ sudo gdb /usr/bin/compiz /tmp/unity-crash/CoreDump GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

Will do. Thanks for the directions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- dae

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

Will try to generate another bug. Meanwhile here's the printout from the gdb commands: similar to above Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `compiz'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f4ebcc

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

Tried sudo ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash get a drop down message that ubuntu has experienced an internal error. Nothing else. Tried removing the *upload and *uploaded files, same thing. Nothing past the first drop down... Any ideas? Maybe install the new .iso and try ubuntu

[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away

I downloaded a new .iso. same bug occurred on both booting the .iso and booting the install. In Comment #70 Marco suggested: "Can you please open another bug (like "unity crashes in unity::UnityScreen::paintDisplay", using ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash)?" Does not work. I get

[Touch-packages] [Bug 1324257] Re: utopic lubuntu insserv error

Comment #6 how do I tell what the version of dbus is? I tried update-rc.d dbus start 12 2 3 4 5 . and a number of combinations. Unity still does not start, only wallpaper. Is there a "start unity" command? Thanks. -- You received this bug notification because you are a member of Ubuntu Touc

[Touch-packages] [Bug 1357753] [NEW] compiz crashed with signal 5 in g_type_create_instance()

Public bug reported: Booted utopic updated to -8 limux image level, wallpaper no unity panels, so did Ctrl-Alt-F1 and sudo unity. Ctrl-Alt-F7 to get back to graphics screen. Utopic then reported internal error in a normal drop down window. Utopic brought up firefox O.K. and reported error. Fir

[Touch-packages] [Bug 1357753] Re: compiz crashed with signal 5 in g_type_create_instance()

Did Ctrl-Alt-F1 and saw a whole pile of messages from unity trying to start. Earliest error message: "unity is not supported by your hardware" Hello? Unity runs fine with utopic linux-image -5 level and -6 level. How come utopic unity at -8 level has decided that "unity is not supported by you

[Touch-packages] [Bug 1357753] Re: compiz crashed with signal 5 in g_type_create_instance()

Did Ctrl-Alt-F1 and saw a whole pile of messages from unity trying to start. Earliest error message: "unity is not supported by your hardware" Hello? Unity runs fine with utopic linux-image -5 level and -6 level. How come utopic unity at -8 level has decided that "unity is not supported by you

[Touch-packages] [Bug 1357746] Re: unity fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1

On starting unity with linux-image -8, whole screenful of messages flash by. Finally trying to read them (at 1920x1080 default resolution that's a bear) I see near the beginning: "Your hardware does not support unity" How come this same hardware supported unity on linux-image -5? This hardware

[Touch-packages] [Bug 1357746] Re: unity fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1

Tried latest .iso at linux-image -8 utopic-desktop-amd64.iso 16-Aug-2014 wallpaper only, unity didn't start. Selected lines from Ctrl-Alt-F1 copied by hand, I don't know what log this data may be in: [drm: init-ring-control] *ERR0R* rendir ring initialization failed [drm: i915_g

[Touch-packages] [Bug 1357746] Re: unity, (compiz) fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1

This utopic install was initially linux image 3.16.0-5. Updated to -7 compiz and unity fail, X11 running fine to desktop no panels. Updated to -8 first boot from dead cold overnight boots O.K. Reboots compiz and unity fail. Externally acts like a race condition that works sometimes other times n

[Touch-packages] [Bug 1357753] Re: compiz crashed with signal 5 in g_type_create_instance()

Did Ctrl-Alt-F1 and saw a whole pile of messages from unity trying to start. Earliest error message: "unity is not supported by your hardware" Hello? Unity runs fine with utopic linux-image -5 level and -6 level. How come utopic unity at -8 level has decided that "unity is not supported by you

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Downloaded same day's i386 32 bit. 32 bit .iso booted to normal desktop, compiz, unity, and installed just fine. I've been running 64 bit on this Intel Core 2 Duo 3 gHz 4 gb all along just fine up to and including 3.16.0-6. Looking at various posts, there's been a compiz change -- You rece

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

32 bit 3.16.0-9 boots and runs fine (for a development release) using it right now. Downloaded and tried both 32 and 64 same day, 64 fails 32 runs. What's the difference between the drivers for 32 bit and 64 bit? How do I tell which driver is being used? Thanks for looking at this bug. -- You

[Touch-packages] [Bug 1357746] Re: unity, (compiz) fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1

3.16.0-9 i386 32 bit boots normally. Very rarely boots to desktop and cursor no unity. 3.16.0-9 amd64 always boots to desktop no unity. X is up, compiz hence unity are not. 3.16..0-8 rarely boots to unity, usually to desktop and cursor only. Viewing utopic as a black box, characteristics are t

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Updated 22 August: 3.16.0-10 amd64 .iso boots to desktop, compiz and unity fail. 3.16.0-10 i386 32 bit running as expected (for a development release). Other users see same problem, refer to http://ubuntuforums.org/showthread.php?t=2240600 -- You received this bug notification because you are

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Installed Lubuntu amd64 as well. 3.16.-10 amd64 runs fine, only faster. No compiz. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso bo

[Touch-packages] [Bug 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware

I get a similar compiz error on amd64. In my case, booting 3.16.0.6 kernels or before work fine. Booting amd64 3.16.0-7, -8, -9, -10 kernels on the same install the desktop runs but compiz hence unity do not. Booting the newer .iso the live session fails the same way. Follow through with the in

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

26 August 3.10.6-10 still not running on the amd64 .iso on Lenovo ThinkCentre. Intel Core 2 duo 3.0 gHz 4 mb. Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) Just did an install here today, using the last 3.16.0-6 iso I have saved. Installed, compiz & unity running. Up

[Touch-packages] [Bug 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware

Maybe the "problem description" is invalid, however the "problem" is very real. See also ttps://bugs.launchpad.net/ubuntu/+source/unity/+bug/1359299, confirmed, multiple users report problem. Utopic amd64 does not work on Lenovo ThinkCentre. Intel Core 2 duo 3.0 gHz 4 mb. Intel Corporation 4 Ser

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Out of many boots today, 3.16.0-10 ran once. Almost all the time X is running, desktop is fine, compiz and unity fail. Trying to get compiz and unity running from Ctrl-Alt-F1 or F2 gets a whole screen of messages, including: ... Unity is fully supported by your hardware Unity is not supporte

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Looked at bug #1346096. That user got success with apt-get update, apt- get dist-upgrade. Not me. As of 27 August updates the 3.10.0-10 kernel still fails. Of course, booting the corresponding .iso fails no surprise. On the same install, same everything else but the kernel, selecting 3.10.0-6

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Still trying to get 3.16.0-10 to run unity on Intel Core 2 Duo. Many boots yesterday, just one time 3.16.0-10 ran just fine with 3D hardware support. All the rest, I assume "compiz" has decided that the hardware does not support 3D. It does. Viewing all this as a "black box", what's going on i

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Joseph, on your comment #18, yes, booting with prior kernel 3.16.0-6 works. Like right now. As has all utopic kernels previous to 3.10.0-7. Tried latest 3.17.0-031700rc2-generic on three different installs: 1. On a 3.16.0-9 install, compiz/unity fail as usual. installed 3.17.0-031700rc2-gener

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

3.16.0-6 works for me. Looking at Xorg.0.log - is this the driver that's being used? [ 9.623] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730 [ 9.623] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 (Maarten Lankhorst ) [

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Here's the same thing from 3.16.0-10 where compiz fails and hence unity fails. I'm no developer, looks to me like the same driver works for 3.16.0-6 and fails with 3.16.0-10 ? Am I looking in the wrong place? [ 9.469] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.914-1~exp1ubu

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Stephen, thanks for your interest. Here's EE results from booting 3.16.0-6 which is fully working: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 7.504] Initializing built-in extension MIT-SCREEN-SAVER [ 7.631] (EE) intel: Failed to load module "dri3" (module doe

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

As a computer development engineer, if something failed that ran before, suspect would be whatever was new (kernel in this case). Did the new item fail, or did it react in such a way to cause something else to fail that was running O.K. before? Can you tell if the same Intel driver is being used

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Thanks. If I can do any testing let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in “linux”

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

BTW, if there's any way to try Compiz with bisection, from my past ubuntu testing over the years since Compiz was introduced, Compiz code has a lot of hardware dependencies Just tried 3.16.0-11 updates on 30 August still no go. -- You received this bug notification because you are a member o

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

As far as triangulation from the bird's eye view: utopic fails: ubuntu unity/compiz amd64 after July 31 utopic works: ubuntu unity/compiz amd64 July 31 and before ubuntu unity/compiz i386 today kubuntu amd64 today xubuntu amd64 today lubuntu amd64 today I'm no particular fan of unity, but as a

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

On Intel Core 2 Duo 3.0 gHz Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) Trying 3.17.0-rc3 3.16.0-11.iso actually boots to unity. First time in a month. Very shaky 1920x1024 mouse hardly works. boots to desktop only. No unity. .iso did get unity, install didn't.

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Well, 3.16.0-11 has booted to desktop only, and for the first time booted normally on Intel Core 2 Duo 3.0 gHz. rc3 kernel is also in /boot I select which kernel at boot time..and sets to 1360x768 which the rc3 nomodeset would not do. .iso is http://cdimage.ubuntu.com/cdimage/daily-live/curr

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Next 3 boots unity/compiz failed. Had to do nomodeset to post this comment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso boots to deskt

[Touch-packages] [Bug 1357753] Re: compiz crashed with signal 5 in g_type_create_instance()

This bug may be related: https://bugs.launchpad.net/bugs/1359299 nomodeset on the linux boot line allows unity to run with low res mode. Not useful except for trying bug fixes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1357753] Re: compiz crashed with signal 5 in g_type_create_instance()

linux-image-3.16.0-12 booted O.K. several times this morning. I wouldn't know whether there is actually a fix for compiz or just whether the timing race of compiz/x is better. So as of 3.16.0-12 this problem has not reproduced over several boots. -- You received this bug notification

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

linux-image-3.16.0-12 booted O.K. several times this morning. I wouldn't know whether there is actually a fix for compiz or just whether the timing race of compiz/x is better. So as of 3.16.0-12 this problem has not reproduced over several boots. BTW, 3.17...rc3 still fails unless nomo

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

4 September amd64 .iso boots to flashing desktop, no unity. 3.16.0-12 kernel in the .iso according to ls /boot fails to start unity. My -11 updated to -12 does work. Now the .iso is usually behind apt-get update. Past experience if the .iso isn't running correctly the install won't either. No

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

U + 1 forums for last few days a number of people on a variety of hardware booting to black screen or command line or Anything we can do to test anything? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Joseph, will give them a try. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in Unity: Confirmed Statu

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

Joseph, tried the rc7 and the -7 kernels on a new install which is at -12 level. The .iso boots to desktop so I do a Ctrl-Alt-F1 for a command .ine. The .deb's were previously downloaded with a utopic -12 which works. With the fresh .iso install, no updates, did dpkg -i on the rc7. Booted, hung

[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned

This pc is at DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)" Linux Aspire1 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux model name : Intel(R) Atom(TM) CPU N455 @ 1.

[Touch-packages] [Bug 1228991] Re: compiz crashed with SIGSEGV in _swrast_map_texture()

I'm running Utopic Development now, haven't had this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1228991 Title: compiz crashed with SIGSEGV in _swrast_map_textur

[Touch-packages] [Bug 1324257] Re: utopic lubuntu insserv error

No Unity yesterday 2014 0725 after update to 3.16.0-5-generic #10-Ubuntu. Just wallpaper. Booted in recovery, enabled network, did apt-get update & dist-upgrade no help. No Unity today 20140726 did recovery mode network apt-get update & dist- upgrade Unity did start & run. A bit buggy, single c

[Touch-packages] [Bug 1324257] Re: utopic lubuntu insserv error

Comment #6: dbus exists. It's marked executable. I did sudo ./dbus and can't tell if anything happened? I'll try the update command. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/

[Touch-packages] [Bug 1324257] Re: utopic lubuntu insserv error

Well, I tried: $ update-rc.d dbus start 12 2 3 4 5 . now utopic boots to wallpaper. No unity. Ctrl-Alt-Del gets a window about processes - the window flashes on and off. Any way to undu the update-rc.d dbus start 12 2 3 4 5 This is from 14.04. No big deal to zsync, mkusb, and re-install utop