Thanks Gunnarhj. I will manually add the header next time before I am
ready for submittal.
I am not sure if I need to do anything else for now so I will start looking
into what we need to do to get the gtk3-nocsd changes submitted. I
need to rebuild them using the actual packaging process, test them
again and get them ready to submit. I also need to figure out how
to make a recipe so we can get them back to GitHub where they
came from(I had to make a minor change in the code).
Can not access anydesk / dropbox or see temp sensors etc with Unity anymore
so mixed feelings , Unity had a better Multi desktop / Multi monitor setup
but now that I can not access Dropbox or see my temps Unsure which I should keep trying to use
at least Unity you could separate Programs out onto different workspaces gnome just does not seem to do that
Unity also allowed you to drag and drop from any workspace with out having to physically being at the monitor , gnome I have to guess where the mouse is âŚ
I still prefer Unity over any other desktop even with the compiz bug that goes 100% CPU all the time
Both are gnome screenshotâŚand dropbox etc uses appindicatorâŚthere are two appindicators nowâŚoriginal unity appindicator and ayatana indicatorâŚso itâs possible they are using ayatana appindicators. A simple recompiling will fix the issue.
so I should be looking for a way to install unity appindicator ?
E: Unable to locate package indicator-systemtray-unity
ayatana-indicator-common is already the newest version (0.8.4-4ubuntu2).
gnome-shell-extension-appindicator is already the newest version (41-1).
gir1.2-appindicator3-0.1 is already the newest version (12.10.1+20.10.20200706.1-0ubuntu1).
@mastercatz@khurshid-alam
I am running 22.04 with Unity and it seems to be working fine for me. I just
installed the classicmenu-indicator and it seems to work fine.
I think Khurshid is right and you need to run lightdm instead of gdm.
The gtk3-nocsd patch is tested on Ubuntu Unity in 21.10 as well as
my 22.04 build. I did not want to attach the debdiff and mark it for
patching until the recipe for github is done and whether or not I
can do that or does Khurshid or one of you do that for me.
Let me know and I can submit the changes.
The bug report I created is LP: #1946161
Folks did not hear anything back from my last post.
I need to know if I need to make the launchpad recipe for the gtk3-nocsd changes to
go back to the GitHub from where they came or does someone else need to do it?
Would it be better for me to create my own PPA and put the gtk3-nocsd changes
for Gtk4 support there?
Rudra has remove all gtk3-nocsd support via an update to the Unity dev PPA so
I cannot use the PPA anymore as I need Gtk4 support for gtk3-nocsd.
The code has been ready to submit for quite a while now I just need to know
where to submit it.
Ah, I removed it because there were many complaints and I was asked to remove it until the new version was in place. If you want to upload a new version of gtk3-nocsd, you can upload it to your PPA and Iâll copy it to the Ubuntu Unity PPA (replacing the dummy package), but youâll need to set the version to 5-1ubuntu1, since the dummy packageâs version was 4-1ubuntu1.
Ok not a problem. I currently do not have a PPA set up yet but probably should
make one in the future for my ISO builder app(WolfLandBuilder) as well as other
things like a port of LeoLikâs configurable notify-osd to latest for 22.04.
Probably best to go to the Ubuntu Unity PPA after I rebuild the debâs for
4-1ubuntu2 if thatâs ok. I will have to hand manage the control file and
anything else that references my current version which is 3-1ubuntu2 and
change it to 4-1ubuntu2. Probably not a good idea to change the major version
number again(patch-edit usually increments the minor number and sets the
version for you. For example 3-1ubuntu1 to 3-1ubuntu2). I could either redo
the whole thing based on your version(e.g. 4-1ubuntu1) using patch-edit
which would give us 4-1ubuntu2 or I should be able to manually change the
version in what I already have to 4-1ubuntu2 and just rerun the debuild -S
and pbuilder commands. I not sure this will work and may have to getsource
your updated version and repopulate all of the needed files(I will have to see
what happens). Using your current source and patch-edit may be the safest
thing to do so I may go that way to stay with Ubuntuâs development process
as close as possible.
I am busy tomorrow morning but will work on it when I get back in the
afternoon. Hopefully I will have it rebuilt for 4-1ubuntu2 and tested
tomorrow(I will have to test it against your 4-1ubuntu1 version) to
ensure it still installs and works properly.
When I get it done and tested I can attach the deb diff to the bug report
LP: #1946161 which I opened for the problem and mark it for patch like
we did last time or how ever you want to handle it.
I will reply again once I get it rebuilt with the new version number and
tested against 4-1ubuntu1 and make sure it installs and works.
Let me know if this is ok or if you want me to do something else.
Spent all night last night and finally was able to hack through the process
and get debuild -S -d done and pbuilder to make debs for impish.
I tested these on an fully updated Ubuntu Unity install with version 4-1ubuntu1
installed and it worked ok.
I have gotten a new debdiff for the fix but still need to create jammy debs and
test them on my 22.04 build against 3-1ubuntu1 and make sure they install and
work and then I can attach the debdiff to my bug report LP: #1946161.
The new version is 4-1ubuntu2 and hopefully will work with both the 4-1ubuntu1
version in 21.10 as well as the 3-1ubuntu1 version in 22.04.
What I did to get things to work:
1- copy the gtk3-nocsd directory and the other 3 files that are gotten if you do
a pull-lp-source to a new directory(pull-lp-source would only get you 3-1ubuntu1).
2-edit debian/changelog and debian/files and change the version number to 4-1ubuntu2
3-rename the 3.orig file to 4.orig
4-debuild -S -d
5-pbuilder for impish with 4-1ubuntu2 .dsc file.
6-copy the 3.orig file from my original directory to new directory(needed for debdiff)
7-create the debdiff.
This is a best a hack but it seems to work ok and will try and get the 22.04 build and testing
done today and get the debdiff attached to my bug report and marked for patch.
Let me know if you have any questions or concerns or need me to do something different.
Ok we are good to go. I completed the build for jammy and tested it on
WolfLand 22.04 Unity against 3-1ubuntu1(the original version without
GTK4 support).
Testing went without issue.
I have attached the debdiff to LP: #1946161 so if someone will check
it over for me and sponsor it I would appreciate it.
Let me know if there are any issues or changes required.
I need to check into getting the one error I found in the code
corrected on the original GitHub unless we are at some point
going to create a recipe to it so that it updates from LP.
Here are the links to the new 4-1ubuntu2 version debs on my dropbox.
https://www.dropbox.com/s/dk9sxzahdpxdkuc/gtk3-nocsd_4-1ubuntu2_all.deb?dl=0
https://www.dropbox.com/s/5x02wa9j2eiwc07/libgtk3-nocsd0_4-1ubuntu2_amd64.deb?dl=0
You can put these in the dev PPA and they have been tested to install over 4-1ubuntu1.
This should fix the problem until we can find out what happened to Khurshid-alam.
I must have a recipe to the GitHub where we got the code before I can submit
back to the open stream in 22.04
Hi @bbogert24, tried extracting the binary packages you provided to make source packages and it looks like the compiled shared lib (LD file) will only work on amd64 PCs. It would be great if you could upload the source package to ppa:ubuntu-unity-devs/stable, which Iâve given your Launchpad account bbogert24 access to.
Power has been down due to a winter storm on Sunday and part of today
so I got a late start.
What exactly is a source package? I have a tar.gz of the build directory
the 4.orig file the debian.tar.xz file and the .dsc file(what would be downloaded
if you use pull-lp-source) but cannot figure out how to get it uploaded to the
PPA.
I tried dput but it only accepts .changes files and I am not sure what makes them
(maybe bzr builddeb?). To run bzr builddeb I need to have a branch etc.
Do I need to make a branch and use bzr builddeb and submit the .changes file to
the PPA or is there another way to get my tar.gz file there?
If you need the gtk3-nocsd.c file I have that as well.
If I need to be building arm64 debs too let me know as I can setup pbuilder to
do that also but cannot test them as I donât have any arm64 machines.
