It may be too late, but please check if
reboot=pci kernel option could solve the reboot issues...
Regards.
Type: Posts; User: tista; Keyword(s):
It may be too late, but please check if
reboot=pci kernel option could solve the reboot issues...
Regards.
@aljosa2,
Just googling, these posts might be useful for you?
http://mashu.github.io/2015/12/19/Debian-Ideapad-Y700.html...
@fthx,
I think you can file a launchpad bug report related to just Gnome-Shell only... Devs (or other people) may find which codes were "truly" related to this issue even if it will need a bit...
For example, my VAIO Z 2011 runs like this chart:
http://s10.postimg.org/49hxvbm1x/boot_chart.jpg
And top-10 blames are:
450ms dev-dm\x2d3.device
340ms ssh.service
...
@MikeMecanic,
I'm not quite sure about Kylin though, "noplymouth" kernel parameter did not work for stopping plymouth splash?
Or I'm afraid that your kernel had some "wait" caused in your...
Oh forgot to mention...
Gnome-session 3.19.x package provides both GNOME and GNOME on Xorg session entries on Gdm. So if you guys want to load classical gnome-shell/X11 session, please select...
@zika,
Are you using my PPA? : https://launchpad.net/~tista/+archive/ubuntu/wayland
In my PPA, 'gnome-session-wayland' package is now outdated because Next Fedora would do this as well. Yes, now...
Hi,
I just saw your 1st attached screen-shot... Though I have not any clue but it seems there's something wrong with XV output error and/or Xorg user-space driver (especially DRI2 or so), maybe....
@ubername,
Please check your gsettings via:
gsettings get org.gnome.desktop.interface scaling-factor
If it answered uint32 0 (auto-scaling mode), just try to set it as uint32 1 (native screen...
@kansasnoob,
Thanks for your info...
And today I've checked gnome-flashback-metacity session as well.
In my case, I've rebuilt some flashback packages with git codebase and now it works almost...
Greetings,
Today Matthias Clasen, the lead Gtk+ developer, confirmed that issue (drawn solid background & thick border around the windows) as 'downstream issue'.
So he changed bug status on Gnome...
@PaulW2U,
Please let me be clear,
This happened in Gome-Shell with Adwaita, too?
Anyway this might be caused new ubuntu specific patch what unveiled from 3.18.5-1ubuntu1 package:
diff --git...
@sammiev,
This is because Ubuntu contributors only added gschema keys for Unity-settings-daemon instead of patching gsd-power-manager.c. For example, 'button-power', 'button-sleep' ...etc.
But...
@Chanath,
It's the warning from pygobject. Pygobject now warns if gi codes didn't explicitly require a version before importing.
So we don't have to worry about it, Python apps would work...
@sammiev,
Thanks for the info of daily-build... :)
OK. Let's play.
Regards.
Greetings,
Now I'm moving all packages to xenial...
https://launchpad.net/~tista/+archive/ubuntu/wayland
Thanks for head up.:p
Best Regards.
Greetings,
Please git it a try:
mv ~/.config/dconf/{user,user.bak}
This renames dconf file from 'user' to 'user.bak'. Sometimes it might be useful within dist-upgrade for Unity7...
And...
Greetings,
Grub for EFI is named grub-efi-amd64.
Regards.
Ah, it might be a rare case unfortunately... ;)
Regards.
Tista
Hi syntaxerror74,
Sounds strange...
Because Wily still stacks with Packagekit 0.8.17-4ubuntu6~gcc5.3, as launchpad showed:
https://launchpad.net/ubuntu/+source/packagekit
So where did you do...
@harry332,
Thanks for the head up, just now I've tried proposed 4.2.0-15.18 and seems works well on my Dell XPS11 (Haswell graphics).
But I'm running Gdm 3.18.0, Gtk+ 3.19.0, Gnome-Shell 3.18.0,...
Greetings,
I now saw the proposed dfsg~0-0ubuntu3 version on launchpad, too.
Hmm... They just only go back to the start point of fixing *true* bug. Unfortunately they didn't fix the EPS bug...
Greetings,
Today I've tried to upgrade whole Wily Gnome, then
libgs9-common seems to need adding a lot of packages... :(
All I want to install lbgs9-common is to install gimp, gnome-document...
@fjgaude,
gdisk could work to write partition-table?
Regards.
Hi ventrical,
After several times of hot reboot, shutdown, cold boot, AC pluged/unpluged, I could not reproduce this anymore. So it might be an accidentally happening, I hope. ;)
Best Regards.