[Bug 1946161] Re: Add GTK4 support
Folks, Please just ignore for now. We need a recipe done and have not heard back from the package maintainer. I am going to give debs to Ubuntu Unity so they can put them in their PPA and get the fix to the users and will deal with getting the recipe done when we figure out what has happened to the maintainer. I will uncheck the patch box and will try to submit to the open stream when we get the recipe issue solved(need to go to GitHub from where we got it). Sorry for the confusion(I'm a noob). Brett "WolfMan" Bogert ** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946161 Title: Add GTK4 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk3-nocsd/+bug/1946161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946161] Re: Add GTK4 support
This fix adds nocsd support for GTK4 as well as fixes an logic error in gtk_window_set_titlebar in the original code taken from https://github.com/ZaWertun/gtk3-nocsd. Attaching debdiff for version 4.1ubuntu2. This has been tested on Ubuntu Unity 21.10 with new version 4-1ubuntu1 installed as well as WolfLand 22.04 Unity with version 3-1ubuntu1 installed. gtk3-nocsd testing worked as designed. ** Patch added: "Add GTK4 support for gtk3-nocsd" https://bugs.launchpad.net/ubuntu/+source/gtk3-nocsd/+bug/1946161/+attachment/5554177/+files/gtk3-nocsd-4-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946161 Title: Add GTK4 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk3-nocsd/+bug/1946161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946794] Re: unity-tweak-tool: GLib-GIO-ERROR
Sebastien, Got the changes done and tested but could not get the patch header via quilt to work so we are sans patch header. Clearly the other patch writers have another way to get a header into the patch so if we can find out how they are doing it I will be glad to add it and redo the debdiff. Built using pbuilder and debuild. Installed via gdebi. Tested all 3 selections of antialiasing as well as all 4 selections of hinting as well as other items that I needed to change. Works as intended and I will attach the debdiff to the bug report. Let me know what I need to do next. ** Patch added: "more new font schemas changes" https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946794/+attachment/5545401/+files/unity-tweak-tool_0.0.7+-0ubuntu10.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946794 Title: unity-tweak-tool: GLib-GIO-ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1946794] Re: unity-tweak-tool: GLib-GIO-ERROR
Sebastian, Not a problem. I will look into it and see if I can get the needed changes tested and try to get a debdiff for you. Thanks for your help, Brett "WolfMan" Bogert bboger...@gmail.com On 10/13/21 2:57 AM, Sebastien Bacher wrote: > Hey, so I've been uploading patches suggested by contributors over a few > revision but I don't have time to do the testing. It seems like those > iteration didn't really work out though I'm going to step out of > uploading fixes until someone comes with a proper debdiff tested in > which case I'm happy to help with the sponsoring > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946794 Title: unity-tweak-tool: GLib-GIO-ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946794] [NEW] unity-tweak-tool: GLib-GIO-ERROR
Public bug reported:
unity-tweak-tool_0.0.7+-0ubuntu9 is giving an GLib-GIO-ERROR:
(unity-tweak-tool:8927): GLib-GIO-ERROR **: 15:26:30.421: Settings schema
'org.gnome.desktop.interface' does not contain a key named 'antialiasing'
Trace/breakpoint trap (core dumped)
This is probably coming from
/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/theme.py which
is still referencing "antialiasing" and "hinting" instead of "font-aliasing"
and "font-hinting" as in the new schema in desktop.interface:
diff theme.py theme.py.fixed
166c166
< if gsettings.antialiasing.get_string('antialiasing') == 'none':
---
> if gsettings.antialiasing.get_string('font-antialiasing') == 'none':
168c168
< elif gsettings.antialiasing.get_string('antialiasing') == 'grayscale':
---
> elif gsettings.antialiasing.get_string('font-antialiasing') ==
> 'grayscale':
170c170
< elif gsettings.antialiasing.get_string('antialiasing') == 'rgba':
---
> elif gsettings.antialiasing.get_string('font-antialiasing') == 'rgba':
174c174
< if gsettings.antialiasing.get_string('hinting') == 'none':
---
> if gsettings.antialiasing.get_string('font-hinting') == 'none':
176c176
< elif gsettings.antialiasing.get_string('hinting') == 'slight':
---
> elif gsettings.antialiasing.get_string('font-hinting') == 'slight':
178c178
< elif gsettings.antialiasing.get_string('hinting') == 'medium':
---
> elif gsettings.antialiasing.get_string('font-hinting') == 'medium':
180c180
< elif gsettings.antialiasing.get_string('hinting') == 'full':
---
> elif gsettings.antialiasing.get_string('font-hinting') == 'full':
Sorry for the late bug report but got tied up working on gtk3-nocsd for
GTK4.
If you don't have a Unity desktop to test on and want to test your changes
before commit I have a 21.10 machine setup with Unity for testing purposes
and will be glad to test it for you if needed.
Thanks,
Brett "WolfMan" Bogert
bboger...@gmail.com
** Affects: unity-tweak-tool (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946794
Title:
unity-tweak-tool: GLib-GIO-ERROR
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946794/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946477] Re: package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade: installed unity-tweak-tool package post-installation script subprocess returned error exit status 1
Now that I have some time to look at the problem it seems that the post-install
is failing with the following error:
File
"/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/gsettings.py",
line 109
antialiasing = gnome('desktop.interface’)
^
SyntaxError: EOL while scanning string literal
If you edit the gsettings.py file with gedit you can see that the end
parentheses is showing
in pink instead of white.
Don't know if this is a problem with the patch file but somehow we are picking
up an EOL
character which is causing the closing parenthesis to be shown as pink instead
of
white(maybe interpreted as an EOL signal or something like that).
As far as I can tell the coding changes seem to be correct for the moving of
the schema
from "xsettings" to "desktop.interface" but I am a noob so what the hell do I
know.
If I can gather more information or anything let me know.
Brett "WolfMan" Bogert
bboger...@gmail.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946477
Title:
package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade:
installed unity-tweak-tool package post-installation script subprocess
returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946477/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946477] Re: package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade: installed unity-tweak-tool package post-installation script subprocess returned error exit status 1
I think the title pretty much says it all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946477 Title: package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade: installed unity-tweak-tool package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946477] [NEW] package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade: installed unity-tweak-tool package post-installation script subprocess returned error exit status 1
Public bug reported:
The title pretty much says it all.
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: unity-tweak-tool 0.0.7+-0ubuntu8
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Oct 8 08:21:22 2021
ErrorMessage: installed unity-tweak-tool package post-installation script
subprocess returned error exit status 1
InstallationDate: Installed on 2021-10-04 (3 days ago)
InstallationMedia: WolfLand 21.10 Unity v1.8b - Release amd64
PackageArchitecture: all
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: N/A
SourcePackage: unity-tweak-tool
Title: package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade:
installed unity-tweak-tool package post-installation script subprocess returned
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: unity-tweak-tool (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package impish third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946477
Title:
package unity-tweak-tool 0.0.7+-0ubuntu8 failed to install/upgrade:
installed unity-tweak-tool package post-installation script subprocess
returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1946477/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946161] [NEW] Add GTK4 support
Public bug reported: Add GTK4 support from: https://github.com/ZaWertun/gtk3-nocsd. This fixes issues with the removal of the Client Side Decorations in GTK4 as well as some window decoration issues. ** Affects: gtk3-nocsd (Ubuntu) Importance: Undecided Assignee: Brett Bogert (bbogert24) Status: New ** Changed in: gtk3-nocsd (Ubuntu) Assignee: (unassigned) => Brett Bogert (bbogert24) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946161 Title: Add GTK4 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk3-nocsd/+bug/1946161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1871963] Re: dpkg fails to install grub-efi-amd64 signed and shim-signed
Rob, Your problem is due to another process having the /var/cache/debconf.dat file in a locked state: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable The original problem reported was due to a syntax error in the code which is now fixed. I have never seen this particular problem before so haven't a clue how to fix it. Normally if you have a file locked during an apt command it is due to another apt process locking it. This could be due to an automated check for update(e.g. apt update) command running when you are trying to do a manual command or from one of the package managers being left open when you are trying to do a manual command. Hope this helps, Brett "WolfMan" Bogert bboger...@gmail.com On 4/10/20 7:42 PM, Rob Frohne wrote: > For me there as no semicolon, but I still get the error. > > rohro@frohro-260:~/Projects/IQ_SDR/Receiver$ sudo vi > /var/lib/dpkg/info/grub-efi-amd64-signed.postinst > frohro@frohro-260:~/Projects/IQ_SDR/Receiver$ sudo apt upgrade -f > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: >clang-tidy-9 clang-tools-9 gnome-software-common libberkeleydb-perl > libcgi-fast-perl libcgi-pm-perl libclang1-9 >libclass-accessor-perl libfcgi-perl libfdk-aac1 libffi6 libmypaint-1.3-0 > libobjc-8-dev libpoppler95 >libpython3.7 libpython3.7-minimal libpython3.7-stdlib > libwxgtk-webview3.0-gtk3-0v5 node-node-uuid > Use 'sudo apt autoremove' to remove them. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] > debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by > another process: Resource temporarily unavailable > Setting up grub-efi-amd64-signed (1.140+2.04-1ubuntu24) ... > debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by > another process: Resource temporarily unavai > lable > dpkg: error processing package grub-efi-amd64-signed (--configure): > installed grub-efi-amd64-signed package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > grub-efi-amd64-signed > E: Sub-process /usr/bin/dpkg returned an error code (1) > frohro@frohro-260:~/Projects/IQ_SDR/Receiver$ > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871963 Title: dpkg fails to install grub-efi-amd64 signed and shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871989] [NEW] dpkg: error processing package grub-efi-amd64-signed (--configure):
Public bug reported: Upon updates on 20200409 I encountered the following error: Setting up grub-efi-amd64-signed (1.139+2.04-1ubuntu24) ... /var/lib/dpkg/info/grub-efi-amd64-signed.postinst: 23: Syntax error: word unexpe cted (expecting ")") dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess ret urned error exit status 2 The problem is being caused by a syntax error in grub-efi-amd64-signed.postint at line 23. Problematic code: case $1 in configure) target=x86_64-efi ;; # Check /boot/grub to see if we previously installed to an ESP. We don't # want to trigger the install code just by installing the package, # normally the installer installs grub itself first. if test -e /boot/grub/$target/core.efi; then /usr/share/grub/grub-check-signatures /usr/lib/grub/grub-multi-install --target=$target fi ;; esac Corrected code: case $1 in configure) target=x86_64-efi # Check /boot/grub to see if we previously installed to an ESP. We don't # want to trigger the install code just by installing the package, # normally the installer installs grub itself first. if test -e /boot/grub/$target/core.efi; then /usr/share/grub/grub-check-signatures /usr/lib/grub/grub-multi-install --target=$target fi ;; esac Problem was found and fixed using shellcheck and geany IDE. I changed the code re-ran the upgrade command verified the boot partition via the dialog and rebooted and it worked fine. Thanks, Brett "WolfMan" Bogert ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871989 Title: dpkg: error processing package grub-efi-amd64-signed (--configure): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1871989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1845730] Re: ubiquity crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: '/sbin/udevadm': '/sbin/udevadm'
Rik, Makes sense as I did all of my initial testing on a machine that is connected via ethernet but my daily driver is connected via wireless. This would explain why I did not catch this before the beta. On 9/30/19 2:31 AM, Rik Mills wrote: > Probably obvious, but I'll say for the record. I see this on a laptop > with failure to load try/install screen, and launch from live session, > where the laptop has only wireless to configure. Not seen on a Vbox VM > with its emulated ethernet connection there. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845730 Title: ubiquity crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: '/sbin/udevadm': '/sbin/udevadm' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1845730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
After not be satisfied with any of the above workarounds to the problem I decided to take a look at the problem and see if I could come up with a "cleaner" workaround or fix. I found that this problem occurs in Ubuntu 16.04 with Unity Gnome 3.18 GnomeShell Gnome 3.20, Budgie Gnome 3.18 and Fedora 24 Beta. After some troubleshooting I found the following solution that does not require changing executable permissions or removing packages: 1- Make a backup copy of the smb.conf file in /etc/samba. 2- Edit the /etc/samba/smb.conf file using your favorite editor and add the following line under the "[global]" statement: name resolve order = wins lmhosts bcast The file should look like this: [global] name resolve order = wins lmhosts bcast 3- Save the file and reboot. The problem should be fixed and you should notice that the "Network" Icon and label shows up much quicker in your file browser than before and the 100% CPU usage is gone. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
I am also having this problem on multiple machines. Every time I hear the fans running on high (except when I am remastering) its due to this bug. I am running 16.04 64bit with Unity desktop. Just wanted to add myself to the list of those seeing the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string
Folks, Updates had been working fine for me until today (5/19/2016). I updated my machines last night(all 11 of them) and now all are experiencing the aforementioned problem with 100% CPU usage from appstreamcli. It appears that in my case at least that something applied last night must be triggering the problem as I have had no problems with apt update until today. I was able to "Ctrl C" out of the update command and install some updates but have to "assume" that I had gotten them all since the update command never completed. I will try and get the above fix applied to at least some of my machines tomorrow. How will users be able to apply the fix if they can't get past the apt update command hanging (other than manual intervention that is)? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs due to strdup on non-NULL terminated string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521132] Re: Failed to install Xenial in UEFI mode, failed with "grub-efi-amd64-signed package failed to install into /target/"
I am also seeing this with the beta2 image. Non-UEFI installs work fine but any attempt to install with UEFI fails with the reported error: The 'grub-efi-amd64-signed' package failed to install into /target/. Without GRUB boot loader, the installed system will not boot. I have tried installing to a completely naked SSD (e.g. no partitons created before install) and was connected to the internet during the install so EFI partition corruption and not being connected to the internet don't seem to be the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521132 Title: Failed to install Xenial in UEFI mode, failed with "grub-efi- amd64-signed package failed to install into /target/" To manage notifications about this bug go to: https://bugs.launchpad.net/grub-installer/+bug/1521132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506587] Re: Unity Desktop does not respect cursor theme after update
Sebastien, I installed the Ultimate-White24 cursor theme into the /usr/share/icons/ directory. I then used "sudo update-alternatives --install" command to add the cursor theme into the alternatives. I then used "sudo update-alternatives --config x-cursor-theme" to update the cursor theme to be the system wide cursor. Lastly I used Unity-Tweak-Tool to select the "Ultimate-White24" cursor for the Unity desktop. The cursor theme was working fine until the above mentioned updates were installed and the problem appeared. I agree that the update to unity-settings-daemon is the most likely suspect. I only updated my "daily driver" machine with the updates and kept my "build server" back from being updated until last night. The build server was correctly displaying the cursor theme in all cases until I updated it last night and now it shows the problem as well. Thanks, Brett -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506587 Title: Unity Desktop does not respect cursor theme after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1506587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506587] Re: Unity Desktop does not respect cursor theme after update
Sebastien, After looking at the code involved as well as information on how to set up the Xserver for the cursor size/name I found the following workaround: Add the following to the "/etc/X11/Xresources/x11-common" file: Xcursor.size: 24 Xcursor.theme: Ultimate-White24 Of course this is what the newly added code is supposed to be doing so I am just manually informing the Xserver of the same information. Thanks, Brett -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506587 Title: Unity Desktop does not respect cursor theme after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1506587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1506587] Re: Unity Desktop does not respect cursor theme after update
Sebastien, Here is the output of the gsettings command: ~$ gsettings get org.gnome.desktop.interface cursor-theme 'Ultimate- White24' I checked that this was set correctly before I opened the bug report. Thanks, Brett On 10/19/2015 11:50 AM, Sebastien Bacher wrote: > gsettings get org.gnome.desktop.interface cursor-theme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506587 Title: Unity Desktop does not respect cursor theme after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1506587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506587] [NEW] Unity Desktop does not respect cursor theme after update
Public bug reported: After update on 20151015 at 9:54 EST Unity desktop no longer respects cursor theme. Ubuntu release is Wily (e.g. 15.10) beta. Update contained the following packages: Oct 15 09:54 hud_14.10+15.10.20151012-0ubuntu1_amd64.deb Oct 15 09:54 libhud2_14.10+15.10.20151012-0ubuntu1_amd64.deb Oct 15 09:54 libunity-settings-daemon1_15.04.1+15.10.20151012-0ubuntu1_amd64.deb Oct 15 09:54 unity-settings-daemon_15.04.1+15.10.20151012-0ubuntu1_amd64.deb Instead of the correct cursor theme "Ultimate-white24" the default white cursor theme is displayed on the desktop and most GTK3 applications. Some applications such as Firefox still show the correct "Ultimate-white24" cursor as long as the cursor stays in the application but changes to the default white cursor if the cursor moves to the window decoration or desktop. Unity Tweak and dconf-editor show that the cursor theme is set to "Ultimate-white24" and the alternatives (e.g. update-alternatives --config x-cursor-theme) also show the cursor theme to be "Ultimate-white24". At the Unity Greeter (e.g. Lightdm) the cursor theme is correct but it changes to the default white cursor as soon as the login is started. Let me know if I can provide any more information, screenshots etc. Thanks ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems fsck from util-linux 2.26.2 /dev/sda2: clean, 418973/13582336 files, 9730415/54308096 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Oct 15 13:52:02 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3180] InstallationDate: Installed on 2015-09-29 (16 days ago) InstallationMedia: WolfLand-15.10-Elite-v1.1b2 15.10 - Release amd64 MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=9d364344-d083-4d67-a7da-9e19332b6f35 ro quiet splash SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX/GEN3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd01/06/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX/GEN3R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Oct 15 13:22:25 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: radeon ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506587 Title: Unity Desktop does not respect cursor theme after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1506587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439860] Re: Gnome Flashback Metacity: Artifacts on all metacity windows
A bit more info. I found that enabling the use dark variant in the terminal options make the problem disappear for the terminal. I then used Tweak Tool to enable the Global Dark option and the problem disappears altogether. I then disabled Global Dark option from the Tweak Tool and chose the Vertex-Dark theme and the problem re-appears. So in short enabling Global Dark in the Tweak Tool makes the problem disappear in all windows and enabling use dark variant in the terminal options makes the problem disappear for the terminal window only. Hope this helps narrow things down a bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439860 Title: Gnome Flashback Metacity: Artifacts on all metacity windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439871] [NEW] Gnome Flashback Metacity: Gradient/Box Shadow on Panels gives incorrect black background
Public bug reported: In Gnome Flashback Metacity Vivid 15.04 Gradient/Box Shadow gives incorrect black background. Theme used is Vertex pr Vertex-Dark for Gtk3.14. Panel background should be gray in color not black. Problem is related to using Gradient/Box Shadow in the theme code for the panels. I am opening this bug report at the theme designers request as he states that is does not work as it should and he cannot style it properly. I will attach 2 screenshots of the problem. Note the black background on the panels where they should be gray. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Thu Apr 2 17:35:06 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] [1002:4c66] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Compaq Computer Corporation Device [0e11:0860] InstallationDate: Installed on 2015-03-03 (30 days ago) InstallationMedia: WolfLand-Gnome-v1.8b1x86 15.04 - Release i386 Lsusb: Bus 001 Device 002: ID 050d:2103 Belkin Components F7D2102 802.11n N300 Micro Wireless Adapter v3000 [Realtek RTL8192CU] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Pavilion zt3300 (DN545AV) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic root=UUID=ec3961a8-08b6-4895-8b59-6f535d966cc1 ro forcepae quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2004 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68BAL Ver. F.42 dmi.board.name: 0860 dmi.board.vendor: COMPAL dmi.board.version: 8051 Version 24.54 dmi.chassis.type: 10 dmi.chassis.vendor: COMPAL dmi.chassis.version: NULL dmi.modalias: dmi:bvnHewlett-Packard:bvr68BALVer.F.42:bd05/07/2004:svnHewlett-Packard:pnPavilionzt3300(DN545AV):pvrF.42:rvnCOMPAL:rn0860:rvr8051Version24.54:cvnCOMPAL:ct10:cvrNULL: dmi.product.name: Pavilion zt3300 (DN545AV) dmi.product.version: F.42 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Apr 2 17:00:25 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputLVDS S-video VGA-0 xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu vivid ** Attachment added: Screenshot of panels with incorrect black background https://bugs.launchpad.net/bugs/1439871/+attachment/4364701/+files/Screenshot%20from%202015-03-02%2021%3A52%3A36.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439871 Title: Gnome Flashback Metacity: Gradient/Box Shadow on Panels gives incorrect black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439860] [NEW] Gnome Flashback Metacity: Artifacts on all metacity windows
Public bug reported: I am getting a light colored artifact around all metacity windows. Theme being used is Vertex or Vertex-Dark for Gtk3.14. Workaround is to restart metacity using metacity --replace from terminal which only works until terminal is closed. This problem has been intermittent all of Vivid 15.04 but has become all the time since Beta2 updates. I will attach a screenshot of the problem to the bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Thu Apr 2 17:19:46 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] [1002:4c66] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Compaq Computer Corporation Device [0e11:0860] InstallationDate: Installed on 2015-03-03 (30 days ago) InstallationMedia: WolfLand-Gnome-v1.8b1x86 15.04 - Release i386 Lsusb: Bus 001 Device 002: ID 050d:2103 Belkin Components F7D2102 802.11n N300 Micro Wireless Adapter v3000 [Realtek RTL8192CU] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Pavilion zt3300 (DN545AV) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic root=UUID=ec3961a8-08b6-4895-8b59-6f535d966cc1 ro forcepae quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2004 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68BAL Ver. F.42 dmi.board.name: 0860 dmi.board.vendor: COMPAL dmi.board.version: 8051 Version 24.54 dmi.chassis.type: 10 dmi.chassis.vendor: COMPAL dmi.chassis.version: NULL dmi.modalias: dmi:bvnHewlett-Packard:bvr68BALVer.F.42:bd05/07/2004:svnHewlett-Packard:pnPavilionzt3300(DN545AV):pvrF.42:rvnCOMPAL:rn0860:rvr8051Version24.54:cvnCOMPAL:ct10:cvrNULL: dmi.product.name: Pavilion zt3300 (DN545AV) dmi.product.version: F.42 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Apr 2 17:00:25 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputLVDS S-video VGA-0 xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu vivid ** Attachment added: Screenshot from 2015-03-21 11:12:18.png https://bugs.launchpad.net/bugs/1439860/+attachment/4364663/+files/Screenshot%20from%202015-03-21%2011%3A12%3A18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439860 Title: Gnome Flashback Metacity: Artifacts on all metacity windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
Raymond, Monday I concentrated on trying to make any progress on getting HDMI to output sound from my video card without losing the first 1 or 2 seconds of it. This is what I tried: ALSA: Position fix quirking - No Effect Pulseaudio: turned off timer scheduling - No Effect commented out module load for suspend on idle - No Effect installed pavucontrol and tried changing setting etc - No Effect General: Completely removed Wine and install fglrx-updates - No Effect I've done all I can except kernel driver patching and I just can't get the HDMI audio on the video card to stop dropping the first 1 to 2 seconds of audio(maybe PCI bus latency or something ?). This happens with the System Ready sound and in the desktop and even playing sounds using aplay in the terminal. Do I need to raise a bug on this HDMI Latency problem ?. I also ran into a problem when disabling and then re-enabling the onboard sound. It appears that the default device is correct but the System Ready sound is still being output on the previous device(e,g, if I disable onboard sound in the BIOS to force output to HDMI it does not return to the onboard sound when the onboard sound is re-enabled and is still outputting on the HMDI device despite that the default device is the onboard sound and no longer the video card). Do I need to raise a bug on this as well ?. While debugging I also noticed that the fglrx-updates does not have the fields for audio like the open source driver does. I am currently using xrandr to turn the HDMI audio off so that the onboard sound can be used by adding it to startup applications. I still don't get the System Ready sound output but at least I get my desktop notifications output. I will not be able to do this when the problem with fglrx and wine is fixed(wine is already fixed, fglrx will be next year I hear). I did a clean install last night and will use xrandr to disable the HDMU audio output for the time being. This will only work until the fglrx/wine dependancy problem is fixed and I can run the proprietary driver again. Let me know if you need any thing else. Sorry for the bad formatting (someone should shrink the Add comment box to the wraparound size so that formatting takes care of itself). Once a software developer/architect always a software developer/architect. Thanks again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
Raymond, I spent most of the day today (Sunday) trying to see if I could make any progress toward making the combined digital audio over the DVI to HDMI or HDMI to HDMI issues I am having any better(e.g. no System Ready sound without disabling the onboard sound in the bios and loss of the first 1 to 2 seconds of audio when output is initiated) and I am sad to say I made little to no progress. I made multiple attempts to force HDMI to be default using methods I found that worked for others with no progress. I also read a butt load of ALSA and Pulseaudio tips, tricks and bug reports as well as design documentation from ALSA. I figured if I could get the HDMI digital sound on rhe Video card working properly I would not need the analog as default for anything other than the inputs (non-linear video editing and such). I also wanted to try the fglrx or fglrx-updates driver but there is a problem with dependencies and Wine that prevents installing the driver if Wine is installed. A few issues with HDMI were solved by using the fglrx proprietary driver so I thought I would give it a try until I ran into the dependency problem. About the only thing I accomplished today was to find out that even if the alc892 chip is disabled on the motherbord to force the HDMI to the default (e.g. 0) entry when the alc892 chip is re-enabled the sound stays on HDMI at least from the System Ready sound standpoint. I checked the /proc/ asound card entries and the alc892 was listed at card 0 so I am not sure how the System Ready sound is still being output via the HDMI output. Other sounds played by the sox play command seem to be coming out at the analog green output despite the desktop being set to HDMI in the System Settings Sound dialog(AARRGGHH). Oh well at least I am learning a bit about the linux sound systems(lol). I will spend the rest of the evening backing up this system in case we need to do anything nasty that might take it down and will make a new up to date respin on my build server in case I need to reinstall the OS at some point(e.g. we will be able to do destuctive testing if needed). Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
** Attachment added: xrandr --verbose for HDMI combined video and audio cable https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+attachment/4265998/+files/Bug-1394711_HDMIcombinedVideo-Audio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
** Attachment added: xrandr --verbose for DVI to HDMI video cable and analog audio cable https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+attachment/4265997/+files/Bug-1394711_DVI-to-HDMI-Video_Analog-Audio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
** Attachment added: xrandr --verbose for VGA video cable with analog audio cable https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+attachment/4265994/+files/Bug-1394711_VGA-Video_Analog-Audio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
Raymond, I have performed the requested data captures and will attach them. I took a look at the xrandr command and decided to try a little troubleshooting on my own and found that the following xrandr command resolves the problem until the system is shutdown or rebooted (e.g. the System Settings sound tests pass and the System Ready sound is output if I logout): xrandr --output DVI-0 --set audio off So it appears that the underlying code for the audio = auto setting for DVI-0 is incorrectly determining that the setting for this configuration(e.g. DVI to HDMI with analog audio) is on instead of off. I can understand the confusion after looking at the DVI video specification on wikipedia and finding this: DVI-D devices output HDMI signals, many including audio, (examples: ATI 3000-series and NVIDIA GTX 200-series video cards) ,[9] and some multimedia displays input that HDMI signal, including audio, by using a DVI to HDMI adapter. Exact capabilities vary by video card specifications. The only test I have not run is to see if the HDMI video card selection in the System Settings Sound dialog will actually output sound on the DVI to HDMI cable and also resolve the issue. I will try this as soon as I finish attaching the data files and will add another comment to let you know what the outcome of the test is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
** Attachment added: xrandr --verbose for DVI to HDMI video cable and analog audio after xrandr --output DVI-0 --set audio off command https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+attachment/4265999/+files/Bug-1394711_DVI-to-HDMI-Video_Analog-Audio-FIX -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
Ok I have run the aforementioned test with the DVI to HDMI cable and no analog sound cable attached and the System Setting Sound dialog set to the HDMI video card sound chip. This does output sound from the test application but the System Ready sound still appears to be going out the analog output. To clarify the latency problem I have been having using HDMI sound on the video card when the sound test application is run initially the front left sound is missing the front sound. After this it works fine until the System Settings dialog is exited and reentered then the latency problem occurs again. This also causes desktop notifications to be only partially output or not output at all when using the HDMI video card's sound device. This is why I have been using the analog output on the motherboard as the problem does not occur with it.. If you need more information or want me to try something I havn't tried or need me to test a proposed fix let me know and I will do so as soon as I can. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1394711] Re: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
Raymond, Thanks for the quick response. I will gather the data for all three setups VGA video with analog audio, HDMI video with analog audio and lastly HDMI Video with combined digital audio from the video card either this weekend or very early next week. I have one item that I have to get done before I can gather the data but I should have something posted by early next week at the latest. Thanks, Brett On 11/21/2014 02:31 AM, Raymond wrote: post output of xrandr --verbose ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394711 Title: [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394711] [NEW] [HDA-Intel - HDA ATI SB, playback] No sound at all with built in display speakers
Public bug reported: Problem Description: No sound at monitors built in speakers after fresh install of Utopic 14.10 Unity Desktop. Details: After installing Ubuntu 14.10 I had no sound at all from the speakers in my monitor. After troubleshooting I determined that the output from the sound system at the 'green' connector on the motherboard was fine but was not being delivered to the monitors speakers. I then replaced the audio cable from the motherboard to the monitor which did not help. I assumed that the analog input of the monitor had gone bad and removed a HDMI cable from my television and tried using it from the Video Card to the monitor and the sound in the monitor speakers worked(e.g. HDMI with combined Video and Audio signal). I assumed that the analog input in the monitor had gone bad and bought a new HDMI cable and used it from the Video card to the monitor. This did not work well however as I had to disable the audio chip on the motherboard to force the system to use the video card sound functionality to get the system ready sound to work. There was also a large latency when sending the sound signal through the video card to the monitor causing the system ready sound and desktop notifications to be cut off or not output at all. A short time after this I installed the same Utopic 14.10 Unity Desktop onto another computer with a similar monitor and had the same result (no sound through the monitor speakers) and discovered the real cause of the problem. The cause of the problem became appearant on the second install when the system ready sound was played but was cut off after a second or so. After this no more sound at all was output to the monitors speakers. For some reason in Utopic 14.10 the sound input in the monitor is being coupled to the video input making it impossible to use the HDMI input for video and the monitors analog input for sound. The audio input is tracking the video input in the monitor and the audio input is switching from the analog input to the HDMI input if a HDMI video cable is being used. This lead me to the conclusion that code is switching the analog input in the monitor to the HDMI audio input based on HDMI video being used and this was proven by the fact that a VGA (analog) video cable and analog audio cable/input works fine as well as a combined HDMI video/audio cable working (not quite fine but working) and to the conclusion that someone has coupled the Video and Audio inputs of the video monitor in the software in Utopic 14.10. In short the analog audio input in the monitor is being switched to the HDMI audio input if a HDMI video cable is being used reguardless of it actually carrying audio (e.g. in my case a DVI to HDMI cable is only used for video and a seperate analog audio cable is being used to carry the audio signal to the analog input in the monitor). Note that this hardware configuration seemed to work fine in Ubuntu 14.04 LTS (e.g. HDMI video and analog audio) and just appeared after the fresh installs of 14.10. Again this problem does not occur if a VGA video cable and and the aforementioned analog audio cable and input are used and only occurs if a DVI to HDMI video cable and analog audio cable/input on the monitor are used. A HDMI combined video/audio cable works as well other than the undesirable characteristics described above (e.g. having to disable onboard audio to force use of the sound on the video card to get the system ready sound and latency problems with the audio). Hardware specifics: Motherboards are ASUS Sabertooth and m5a97 with ASUS mx279h and mx239h monitors respectively. Monitors are connected via DVI to HDMI video cables and audio is being delivered via an 1/8 stereo audio cable from the green analog output at the motherboard to the analog input of the monitor. I am not sure to who this issue belongs because I could not tell who is switching the audio input in the monitor. It occurs sometime during the playing of the system ready sound (this timing may be specific to my hardware configuration and may occur earlier or later depending upon the relative speed of the system). I also was not sure what data to collect as I could not tell what software subsystem (e.g. ALSA or Display) was responsible for the audio input in the monitor being switched. Please let me know what data I can collect so this problem can be resolved and I can get back to using my DVI to HDMI video cable and analog audio input and still have sound. In the mean time I have to use the VGA (analog) video cable so that the analog input to the monitor can be used as the HDMI combined video/audio cable solution had undesirable side effects. This bug report was originated using the ubuntu-bug command from terminal so I expect that some data was collected but I am not sure if it will be what is needed to resolve the issue. Thank You ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base
Re: [Bug 1299739] Re: general protection fault: 0000 [#1] SMP
Chris, The bios update did the trick and I have seen no more GPF's since applying it. Thanks, Brett Bogert bboger...@gmail.com On 04/21/2014 05:10 AM, Christopher M. Penalver wrote: Brett Bogert, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/comments/7 regarding this being fixed by adjusting a setting in the BIOS. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Tags added: bios-outdated-2301 ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299739 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1299739] Re: general protection fault: 0000 [#1] SMP
Joseph, I continued testing today with the new kernel and burned another 11 CD's and 2 DVD's. No GPF's occurred so I feel pretty confident that the BIOS change solved the issue. I think we can close the bug report and list the cause as ASUS Optimal settings. I may have a weak memory chip or something that is preventing the more aggressive settings from working. We had a 4 day power outage due to an ice storm earlier this year and it may have had a negative effect on the hardware. I will have to run a 24hr memory test on the machine with the more aggressive settings after 14.04 release and see if I need to replace a memory chip or something. I will add an entry to the bug report stating that the problem has not reoccurred and why. I will be more aware and check my hardware and BIOS settings before I bug report another nebulous GPF of this type (e.g. the traceback was instructive and did not indicate any running software process but gut's level OS processes that could be related to BIOS or hardware problem). Thanks for your quick response and help, B.Bogert bboger...@gmail.com On 03/31/2014 05:53 PM, Joseph Salisbury wrote: Are you able to reproduce the GPF? If so, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299739 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299739] Re: general protection fault: 0000 [#1] SMP
Problem seems to be resolved (see above) and was caused by aggressive timing parameters (ASUS Optimal settings) and possible weak or bad memory chip. Once BIOS parameter was changed to ASUS Normal settings the problem resolved itself and no more GPF's were output after burning many more CD's/DVD's. Hardware testing will have to be done after 14.04 releases to verify weak/bad hardware is replaced and I will be more aware that this type of GPF indicates possible BIOS/Hardware issues before I raise another bug report of this nature. Please close this bug report and thanks for the quick response and help, B.Bogert -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299739 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1299739] Re: general protection fault: 0000 [#1] SMP
Joseph, A quick progress report on my testing. So far I have burned 6 DVD's and 11 CD's without any more GPF's and the machine has been rock solid since I changed the BIOS setting. I suspect that the problem has resolved itself with the BIOS setting change but will continue to beat on it to see if I can get the problem to occur again with the ASUS Normal BIOS settings. I noticed that there is a new kernel update in the update queue for tonight (3.13.0.21-43) and I will be updating all 7 build/testing machines tonight and will send more progress info as warranted. If no more GPF's occur before Friday Apr 4th I think we will be safe to close the bug report and blame the issue on aggressive BIOS settings. I will keep machines on the normal timings instead of ASUS Optimal for the duration of my testing until 14.04 releases. Thanks again, B.Bogert bboger...@gmail.com On 03/31/2014 05:53 PM, Joseph Salisbury wrote: Are you able to reproduce the GPF? If so, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299739 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1299739] Re: general protection fault: 0000 [#1] SMP
Joseph, The GPF happened again this morning. I was burning a CD and it completed and made the ding tone and then Unity died and back to the Lightdm login. I tried to bug report it as a duplicate of 1299739 but launchpad oops'ed and lost the report and I did not have time this morning to spend any more time on it. I have made a BIOS change to ASUS Normal settings from ASUS Optimal settings to make sure the problem is not coming from aggressive timings and will burn some more CD/DVD's today to see if I can get the problem to happen again. The GPF happens infrequently so I am not sure how long it will take to reproduce. I have only seen it the two times so far. If it happens again on ASUS Normal settings I will try the upstream kernel version and keep you informed of what happens. Thanks, B. Bogert bboger...@gmail.com On 03/31/2014 05:53 PM, Joseph Salisbury wrote: Are you able to reproduce the GPF? If so, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299739 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1298476] Re: Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown
Edwin, Thanks for the workaround info. Another possible workaround if you don't have any other OS's on your machine (mine are all Ubuntu only) is to use GRUB_DISABLE_OS_PROBER=true thus removing it from grub.cfg making process all together. Of course if you are dual booting Windows or another OS this will not work as GRUB needs to probe for the other OS's in order to add them to the grub.cfg file. So far my machines seem to be working fine as long as I don't install using LVM and it will be interesting to see if the problem crops back up when I do more installs after I remaster when 14.04 releases. Thanks again for the workaround info as per your experience it appears that I may need it in the future. B. Bogert bboger...@gmail.com On 04/01/2014 08:47 AM, Edwin Pujols wrote: I still see the menu even without LVM. My PC is an HP nx7400. As a workaround I followed this: https://gist.github.com/LeahCim/9332432 Also, here's the bug report I filed (in case your problem and mine are the same): https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1273764 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298476 Title: Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299739] [NEW] general protection fault: 0000 [#1] SMP
Public bug reported: I was burning a CD using Brasero when the Unity desktop died and I ended up back at the lightdm login prompt. This was the first problem of this kind since running Trusty and occured since the latest update on 3/29/2014. The system had been completely stable up to this point. Brasero was in the process of verifying the checksum when the problem occured. Brasero version is 3.10.0, kernel version is 3.13.0-20-generic. This is an ASUS Sabertooth motherboard with 4Ghz AMD 8 core and 16Gb of memory. This is my daily use computer and was up for several days before the GPF occured. I am using the updates ATI proprietary driver from the Ubuntu repository. Let me know if I can provide any more information for you . Thanks, B.Bogert bboger...@gmail.com ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sun Mar 30 07:30:15 2014 Failure: oops HibernationDevice: RESUME=UUID=2018acda-0317-40ce-b43d-4165f2056510 InstallationDate: Installed on 2014-03-18 (11 days ago) InstallationMedia: WolfLand-14.04-v1.7 14.04 - Release amd64 MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=089d0b73-5482-4397-b728-01cf55d432b4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: general protection fault: [#1] SMP UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX/GEN3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0305:bd01/17/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX/GEN3R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299739 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296866] Re: Allow unity-panel.menuitem to paint window title text for maximized window in new Unity Decorator(Trusty)
Khurshid Alam is correct. According to the Unity theming documenation
for Trusty 14.04 the panel text should be set by the UnityPanelWidget as
follows:
UnityPanelWidget,
.unity-panel {
background-color: shade (@dark_bg_color, 1.5);
color: @dark_fg_color; /* Text color */ --- ***SHOULD BE SET HERE***
}
but it is actually being set by the UnityDecoration top code here:
/* This will theme the top decoration, so the whole space above the window */
UnityDecoration.top {
border: 1px solid shade (@bg_color, 0.5);
border-bottom-width: 0;
border-radius: 8px 8px 0 0; /* Corner radius, only the top ones should be */
padding: 1px 8px 0 8px; /* This padding will be applied to the content of
the top layout */
background-color: shade (@dark_bg_color, 1.5); /* Decoration background */
color: @dark_fg_color; /* The foreground color will be used to paint the
text */ --- ***ACTUALLY BEING SET HERE ***
text-shadow: 1px 0 #333, -1px 0 #333, 0 1px #333, 0 -1px #333;
}
This makes it impossible to use a dark panel with light window treatment
as the title color for light window treatment is dark making the panel
label (e.g. Ubuntu Desktop) and maximized title unreadable on a dark
panel.
In short the panel text color should be set by the unity panel widget
class not by the unity decoration class.
Since this problem is already bug reported I will not open another bug
report but track progress under this bug report number.
Thanks,
B.Bogert
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296866
Title:
Allow unity-panel.menuitem to paint window title text for maximized
window in new Unity Decorator(Trusty)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296866/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298476] Re: Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown
** Attachment added: fail case grub.cfg file https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298476/+attachment/4048301/+files/m4a785m-lvm-grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298476 Title: Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298476] Re: Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown
After further investigation I found that the problem appears to be related to installing with LVM enabled. When I installed Trusty I encountered a problem (that started in 13.10 sometime between 11/28/13 and 1/19/14) when installing with LVM enabled over a previous LVM enabled installation (also happens if you try to install with LVM enabled over a previous Windows 7 installation). This causes a warning message that the boot partition is not large enough and the installation may fail. On the first three machines I did not install with LVM enabled but on the other four machines I installed with LVM. I normally install with LVM and had no issues until this warning message started sometime between 11/28/13 and 1/19/14 (in saucy 13.10). For some reason the LVM equipped machines are the ones that are showing the menu instead of the countdown. I proved this by reinstalling Trusty on the four machines that were displaying the menu without LVM this time and they now work as intended. I will attach both a pass (e.g. working countdown case: sabertooth-nonlvm-grub.cfg) as well as a failure case (e.g. menu instead of countdown: m4a785m-lvm-grub.cfg) files. If you need me to reinstall with LVM and collect more data let me know . Thanks again, B.Bogert ** Attachment added: pass case grub.cfg file https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298476/+attachment/4048300/+files/sabertooth-nonlvm-grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298476 Title: Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298476] [NEW] Trusty: inconsistent behaviour of GRUB_TIMEOUT_STYLE=countdown
Public bug reported: For some reason GRUB_TIMEOUT_STYLE=countdown is not being treated in a consistant manner on all my machines. On ASUS m4a785m(2), ASUS m5a97(1) and ASUS p8h61m despite having the GRUB_TIMEOUT_STYLE set to countdown and GRUB_TIMEOUT set to 10 in /etc/default/grub I was getting a menu. On ASUS Sabertooth, ASUS a88xpro and another ASUS m5a97 countdown worked as designed. After a bit of trouble shooting I found that the /boot/grub/grub.cfg files on the offending hardware were actually setting the GRUB_TIMEOUT_STYLE value to menu in a OS-PROBER block at the end of the file despite it being set to countdown in the /etc/default/grub file. Since the offending code was in an OS-PROBER block I tried setting GRUB_DISABLE_OS_PROBER to TRUE and running update- grub which corrected the problem. Although this temporarily fixes the problem I do not think it is addressing the real issue which is the inconsistent setting of GRUB_TIMEOUT_STYLE and therefor inconsistant behavior even on different machines of the same hardware. Since ASUS m5a97(2 different machines) exibited both the fail and pass mode I have to think that this is not hardware specific but possibly something going haywire in grub_mkconfig. Here is my /etc/default/grub file with the problem: # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_TIMEOUT_STYLE=countdown GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT=quiet splash GRUB_CMDLINE_LINUX= # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM=0x01234567,0xfefefefe,0x89abcdef,0xefefefef # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass root=UUID=xxx parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY=true # Uncomment to get a beep at grub start #GRUB_INIT_TUNE=480 440 1 # WolfLand specific changes export GRUB_COLOR_NORMAL=light-gray/light-gray export GRUB_COLOR_HIGHLIGHT=magenta/light-gray GRUB_BACKGROUND=/usr/share/backgrounds/warty-final-ubuntu-bt.png Here is the working /etc/default/grub file: # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_TIMEOUT_STYLE=countdown GRUB_DISABLE_OS_PROBER=true GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT=quiet splash GRUB_CMDLINE_LINUX= # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM=0x01234567,0xfefefefe,0x89abcdef,0xefefefef # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass root=UUID=xxx parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY=true # Uncomment to get a beep at grub start #GRUB_INIT_TUNE=480 440 1 # WolfLand specific changes export GRUB_COLOR_NORMAL=light-gray/light-gray export GRUB_COLOR_HIGHLIGHT=magenta/light-gray GRUB_BACKGROUND=/usr/share/backgrounds/warty-final-ubuntu-bt.png Note that the only difference is the GRUB_DISABLE_OS_PROBER=true directive. I can try and recreate the problem and provide /boot/grub/grub.cfg files if needed. lsb-release -rd: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Grub version is 2.02~beta2-7, Almost forgot.. I upgraded 10 machines (9 desktop and 1 laptop) to Ubuntu 12.04.4 last night and set them up to use GRUB_TIMEOUT_STYLE=countdown. All 10 machines worked as expected without any issue (a mixture of MSI and ASUS hardware) so the problem seems to be related to Trusty(e.g. 14.04) only. Thanks, B.Bogert ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298476 Title: Trusty:
