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 o
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 wel
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 gl
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 uplo
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
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’)
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-too
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 zn
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
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 syn
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 (
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
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
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 notificatio
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 trigge
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 t
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
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
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.d
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
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 t
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
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 intermitten
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
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 fir
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 o
** 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 recei
** 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,
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 Sett
** 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, whic
** 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 o
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
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 syst
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.la
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/DV
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" setti
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 w
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 ar
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
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
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.
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 h
** 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/
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
44 matches
Mail list logo
