On 2025-01-24 10:56, Mercurio, Steven W-CTR (FAA) via Cygwin wrote:
I installed Cygwin and was hoping to do what I did a long time ago which is to have an
actual mate desktop as an alt desktop. The XFCE desktop seems to work but not mate. I
also seem to not be able to install the mate
0-1.x86_64. I had 3.4.6
on the old laptop.
My desktop shortcut on the old laptop goes to:
C:\cygwin64\bin\run2.exe --display 127.0.0.1:0.0 /usr/local/bin/emacs.xml
I tried to set this up on the new laptop, and I noticed that "run2" doesn't
exist, but "run" does. I trie
David Karr via Cygwin writes:
> Ok. I forgot I had to add that package.
>
> However, now there's another odd problem. The command line still doesn't
> start anything, but it does print an error message, saying that it can't
> find "/usr/local/bin/emacs.xml". I can copy that file from the old lapt
[Please don't top post on this list. Thanks.]
On 2/22/2024 4:23 PM, David Karr wrote:
Ok. I forgot I had to add that package.
However, now there's another odd problem. The command line still doesn't
start anything, but it does print an error message, saying that it can't
find "/usr/local/bin
otes on it, or something
> > has changed that I'm not aware of.
> >
> > I'm installing Cygwin on a new laptop, version 3.5.0-1.x86_64. I had
> 3.4.6
> > on the old laptop.
> >
> > My desktop shortcut on the old laptop goes to:
> >
> > C:
0-1.x86_64. I had 3.4.6
on the old laptop.
My desktop shortcut on the old laptop goes to:
C:\cygwin64\bin\run2.exe --display 127.0.0.1:0.0 /usr/local/bin/emacs.xml
I tried to set this up on the new laptop, and I noticed that "run2" doesn't
exist, but "run" do
Every three years or so I have to set up a new laptop, and several things
that I only do in that period I either lose the notes on it, or something
has changed that I'm not aware of.
I'm installing Cygwin on a new laptop, version 3.5.0-1.x86_64. I had 3.4.6
on the old laptop.
My deskto
Thank you so much for the link to the github.com/mintty report -- the
best problem
is a known problem :)
I've posted a comment to that report with a little more info.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:http
Am 15.02.2024 um 09:23 schrieb Bruce Jerrick via Cygwin:
Has anyone had this happen:
Sometimes when I have a mintty running, the upper-left quandrant of the
desktop
becomes inert to the mouse -- icons do not respond to hovers or clicks,
and the
desktop background does not respond to a right
Has anyone had this happen:
Sometimes when I have a mintty running, the upper-left quandrant of the
desktop
becomes inert to the mouse -- icons do not respond to hovers or clicks,
and the
desktop background does not respond to a right-click.
The remainder of the desktop behaves normally
cygwin@cygwin.com
> >> Cc: Orit Heimer
> >> Subject: Re: Cygwin64 does not show my desktop directories
> >>
> >> On Wed, 19 Jul 2023 11:52:31 +0300
> >> Orit Heimer wrote:
> >>> Hello to all,
> >>> I am new to Cygwin64 and encountered a
On 2023-07-19 11:20, Voris, Ben via Cygwin wrote:
-Original Message-
From: Takashi Yano
Sent: 19 July 2023 03:15
To: cygwin@cygwin.com
Cc: Orit Heimer
Subject: Re: Cygwin64 does not show my desktop directories
On Wed, 19 Jul 2023 11:52:31 +0300
Orit Heimer wrote:
Hello to all,
I am
> -Original Message-
> From: Takashi Yano
> Sent: 19 July 2023 03:15
> To: cygwin@cygwin.com
> Cc: Orit Heimer
> Subject: Re: Cygwin64 does not show my desktop directories
>
> On Wed, 19 Jul 2023 11:52:31 +0300
> Orit Heimer wrote:
> > Hello to
On Wed, 19 Jul 2023 11:52:31 +0300
Orit Heimer wrote:
> Hello to all,
> I am new to Cygwin64 and encountered a problem.
> I am using a Windows 10.
> I try to get cygwin64 to show my desktop directories.
> I use the following command to change to this directory:
> *cd /cygdri
Hello to all,
I am new to Cygwin64 and encountered a problem.
I am using a Windows 10.
I try to get cygwin64 to show my desktop directories.
I use the following command to change to this directory:
*cd /cygdrive/c/Users/Default/Desktop*
But when I then use *ls* I get nothing.
I suspect this is a
ASSI writes:
> Takashi Yano via Cygwin writes:
>>> 1. Rename /usr/share/locale to something else, like local.bak.
>>> 2. Start mintty in the usual way.
>>> 3. Rename the directory from step 1 back to /usr/share/local.
>>> 4. Work just like the problem never existed either in the shell running
>>> i
y (non-admin) user account, that explains why I am seeing the
>>>>>>> problem there and not on other machines. Before you are going to
>>>>>>> suggest that it's the admin vs. non-admin rights: no, if I create a
>>>>>>> locale.alias
;>>>> suggest that it's the admin vs. non-admin rights: no, if I create a
> >>>>> locale.alias with my user account (either as an empty file or a copy of
> >>>>> the backup file), then the admin account is unable to start a shell in
> >&
start a shell in
>>>>> mintty successfully. I have no idea why the ownership of a file that
>>>>> onnly should get read (and is readable by everyone) would have the
>>>>> effect I'm seeing, but maybe that gives the clue on where to look for a
>&g
ly should get read (and is readable by everyone) would have the
> > >> effect I'm seeing, but maybe that gives the clue on where to look for a
> > >> fix.
> > >
> > > Thanks for the additional information. I tested the following steps
> > > t
why the ownership of a file that
> >> onnly should get read (and is readable by everyone) would have the
> >> effect I'm seeing, but maybe that gives the clue on where to look for a
> >> fix.
> >
> > Thanks for the additional information. I tested the fo
> Thanks for the additional information. I tested the following steps
> to confirm if the problem can be reproduced.
>
> 1. Enable Administrator account.
> 2. Remove all groups from account yano other than Users.
> 3. Install cygwin for all with gettext package as
Takashi Yano via Cygwin writes:
[…]
> Both 4 and 5 successfully open mintty window with shell.
…as they do for me on other machines that have different configuration.
> I wonder what is the difference between my environment and yours.
That way lies madness… and I can't really tell you as this ma
by everyone) would have the
> effect I'm seeing, but maybe that gives the clue on where to look for a
> fix.
Thanks for the additional information. I tested the following steps
to confirm if the problem can be reproduced.
1. Enable Administrator account.
2. Remove all groups from accoun
Takashi Yano via Cygwin writes:
>> 1. Rename /usr/share/locale to something else, like local.bak.
>> 2. Start mintty in the usual way.
>> 3. Rename the directory from step 1 back to /usr/share/local.
>> 4. Work just like the problem never existed either in the shell running
>> inside the mintty or
repost, first attempt to wrong recipient
Weitergeleitete Nachricht
Betreff:Re: gnome-terminal desktop shortcut
Datum: Mon, 2 Sep 2019 16:52:49 +0200
Von:Franz Fehringer
Newsgruppen:gmane.os.cygwin
Referenzen:
This works for me with
- DISPLAY=:0 at
he start of this thread.
>
> the menu entries that you can find under the windows start menu work every
> once in a while, but the majority of the time they do like you say:
>
> 1 nothing
> 2 runs, but black screen
> 3 runs, and window manager comes up (very seldom)
>
> in
they do like you say:
1 nothing
2 runs, but black screen
3 runs, and window manager comes up (very seldom)
interestingly , running "startx" in mintty is 100% working.
I am using the xfce desktop, and this all started on the last cygwin upgrade i
did (which also broke graphics characters
Hi,
TL;DR (The Management Summary) : I installed an old version (dated 2016) of
(all of) Cygwin where KDE does give me the 'full desktop' experience
(single MS-Windows window). Is there a desire for follow up (and more
details), in the sense that current Cygwin might be made to wo
.
Also, after I have to exit from the 'black screen', I get some remaining
'bash.exe' processes left in MS-Windows task manager (regardless of what
desktop environment/desktop manager I tried to start). Sometimes it seems
to help if I kill these off before I retry to start LXD
On Tue, Apr 28, 2020 at 7:11 AM Maarten Hoes via Cygwin
wrote:
> Hi,
>
>
> I tried a few different Desktop Environments for comparison. At least
> GNOME-Openbox, KDE-Openbox, Plasma, and MATE give me a black screen and no
> taskbar/menu, pop-up menu with right-click on backg
Hi,
I tried a few different Desktop Environments for comparison. At least
GNOME-Openbox, KDE-Openbox, Plasma, and MATE give me a black screen and no
taskbar/menu, pop-up menu with right-click on background, etc., but I can
start applications on them if I open a Cygwin prompt through the
I have the LXDE desktop environment installed, every other time I try to
start it (via the LXDE icon under Cygwin/X) it doesn't completely start
up. By that I mean I don't see the LXDE background screen (the screen is
solid black) and a different window manager appears to be runnin
Hi,
When I run XLaunch and choose single window (or use the KDE 'Plasma'
shortcut), I get a black window (or grey, when also supplying '-retro'),
but I am not getting a desktop like when I do when I run KDE on Linux (KDE
taskbar/menu, pop-up menu with right-click on backgroun
Ken Brown via Cygwin writes:
> It's possible that you also need to copy
> /usr/bin/cygwin-console-helper.exe from a recent Cygwin release.
I was stgarting from a 3.1.4 install (and the latest snapshot from
cygwin.com works on the same installation). I'll look at it again
later.
REgards,
Achim.
On 3/13/2020 5:26 PM, Achim Gratz wrote:
Takashi Yano via Cygwin writes:
I guess renaming /usr/share/locale/locale.alias is enough.
Yes it does.
Could you please test if the following cygwin1.dll resolve
the problem?
Mintty doesn't start when I just replace this DLL, I get a Windows error
Takashi Yano via Cygwin writes:
>> I guess renaming /usr/share/locale/locale.alias is enough.
Yes it does.
> Could you please test if the following cygwin1.dll resolve
> the problem?
Mintty doesn't start when I just replace this DLL, I get a Windows error
"0x0022". That usually means I shou
Am 13.03.2020 um 03:01 schrieb Takashi Yano via Cygwin:
> On Fri, 13 Mar 2020 10:03:25 +0900
> Takashi Yano wrote:
>> On Thu, 12 Mar 2020 20:39:39 +0100
>> Achim Gratz wrote:
>>> I don't really want to imagine how you came up with that observation,
>>> but yes, that's the same problem I am facing.
On Fri, 13 Mar 2020 10:03:25 +0900
Takashi Yano wrote:
> On Thu, 12 Mar 2020 20:39:39 +0100
> Achim Gratz wrote:
> > I don't really want to imagine how you came up with that observation,
> > but yes, that's the same problem I am facing. This is my current
> > workaround now:
> >
> > 1. Rename /us
On Thu, 12 Mar 2020 20:39:39 +0100
Achim Gratz wrote:
> I don't really want to imagine how you came up with that observation,
> but yes, that's the same problem I am facing. This is my current
> workaround now:
>
> 1. Rename /usr/share/locale to something else, like local.bak.
> 2. Start mintty i
Am 12.03.2020 um 20:39 schrieb Achim Gratz:
Rainer Emrich writes:
I really don't know if this the same issue. But I had similiar symptom
after upgrade from 3.0.7 to 3.1.4 on Windows 7. The mintty window pops
up, but I got no command prompt. The bash shell used all of one CPU for
ever. I tried
Takashi Yano via Cygwin writes:
> Achim, can you build mintty locally? If so, could you please
> apply attahed patch to mintty 3.1.4 and report the output
> in mintty window?
I guess I can, but it will take time I don't have right now. I'll see
what I can wedge in next week.
What I did figure ou
Rainer Emrich writes:
> I really don't know if this the same issue. But I had similiar symptom
> after upgrade from 3.0.7 to 3.1.4 on Windows 7. The mintty window pops
> up, but I got no command prompt. The bash shell used all of one CPU for
> ever. I tried several things. The solution after hours
On Wed, 11 Mar 2020 20:51:42 +0100
Corinna Vinschen wrote:
> Hi Takashi,
>
> would you mind to take a look? The mutex is only used in
> fhandler_pty_master::pty_master_fwd_thread if the pseudo console is
> used. Unfortunately I don't see the faintest hint in the starce why
> this occurs. It hap
7, Achim Gratz wrote:
>> Achim Gratz writes:
>>>>> There is some undesirable interaction when I try to start mintty from my
>>>>> desktop shortcut. Mintty itself starts OK, but any Cygwin program that
>>>>> mintty starts (whether a shell or something el
18:47, Achim Gratz wrote:
> Achim Gratz writes:
> >>> There is some undesirable interaction when I try to start mintty from my
> >>> desktop shortcut. Mintty itself starts OK, but any Cygwin program that
> >>> mintty starts (whether a shell or something else) j
Achim Gratz writes:
>>> There is some undesirable interaction when I try to start mintty from my
>>> desktop shortcut. Mintty itself starts OK, but any Cygwin program that
>>> mintty starts (whether a shell or something else) just goes into a
>>> spinloop (
Corinna Vinschen writes:
> The following packages have been uploaded to the Cygwin distribution:
>
> * cygwin-3.1.4-1
> * cygwin-devel-3.1.4-1
> * cygwin-doc-3.1.4-1
Unfortunately the problem that I reported already for the 3.1.0 release
persists. When starting mintty from a desk
Hi everyone, I am trying to get the KDE plasma desktop running. I've
installed xorg-server and plasma-desktop and can get simple gui apps
running (e.g. gvim). When I try to run the plasma desktop (from
"Plasma" icon installed in the windows start menu), the KDE logo appears
Takashi Yano writes:
> Does anything change if the registry value ForceV2 is set to 0 under
> HKEY_CURRENT_USER\Console? This disables the pseudo console feature.
No, nothing that I can determine changes, but thanks for the suggestion.
> Note: Do not forget to revert the registry value.
Yup,. re
Corinna Vinschen writes:
>> There is some undesirable interaction when I try to start mintty from my
>> desktop shortcut. Mintty itself starts OK, but any Cygwin program that
>> mintty starts (whether a shell or something else) just goes into a
>> spinloop (Windows says
is some undesirable interaction when I try to start mintty from my
> desktop shortcut. Mintty itself starts OK, but any Cygwin program that
> mintty starts (whether a shell or something else) just goes into a
> spinloop (Windows says it's mostly kernel time). Starting Cygwin
> throug
nteraction when I try to start mintty from my
> desktop shortcut. Mintty itself starts OK, but any Cygwin program that
> mintty starts (whether a shell or something else) just goes into a
> spinloop (Windows says it's mostly kernel time).
Windows version?
> Starting Cygwin
> thr
Corinna Vinschen writes:
> The following packages have been uploaded to the Cygwin distribution:
>
> * cygwin-3.1.0-1
> * cygwin-devel-3.1.0-1
> * cygwin-doc-3.1.0-1
>
There is some undesirable interaction when I try to start mintty from my
desktop shortcut. Mintty itself
This works for me with
- DISPLAY=:0 at toplevel Windows (DOS) level
- Cygwin bin (last) in the Windows (DOS) path
The desktop link is
C:\Tools\Cygwin\bin\run.exe C:\Tools\Cygwin\bin\gnome-terminal.exe
One essential point is to use UTF-8
I have LC_ALL=de_DE.utf8 both at Windows (DOS) and Cygwin
On 2019-09-01 23:14, Amadeus WM via cygwin wrote:
> I installed cygwin 3.0.7 about 2 weeks ago and everything seems fine.
> I start the X server from the command line with startxwin.
>
> What I'd like to do is to set up a desktop shortcut for gnome-terminal.
> I have defin
I installed cygwin 3.0.7 about 2 weeks ago and everything seems fine.
I start the X server from the command line with startxwin.
What I'd like to do is to set up a desktop shortcut for gnome-terminal.
I have defined the DISPLAY=":0.0" option in windows, and from mintty I c
-1.0.4-1
* libxapp-devel-1.0.4-1
* libxapp-doc-1.0.4-1
* marco-1.20.1-1
* marco-devel-1.20.1-1
* mate-applets-1.20.1-1
* mate-backgrounds-1.20.0-1
* mate-calc-1.20.1-1
* mate-common-1.20.0-1
* mate-control-center-1.20.2-1
* mate-desktop-1.20.1-1
* mate-desktop-schemas-1.20.1-1
* mate-dictionary-1.20.0
tepad in the
> example below).
> the 'i' switch is used to indicate that you want to interact with the
> windows desktop
>
> psexec \\192.168.X.xxx -u $username -i $id -d notepad.exe
>
> pause
>
If you want to follow along with Microsoft's own effort/inability t
ssion
$id = $results | Select-String "$username\s+(\w+)" |
Foreach {$_.Matches[0].Groups[1].Value}
Then you can follow up by invoking the windows program (notepad in the
example below).
the 'i' switch is used to indicate that you want to interact with the
wi
On Sat, Mar 17, 2018 at 2:47 PM, mhallnh wrote:
> What's the answer? That CYGWIN sshd can not interact with the Windows
> desktop?
>
It can if it is run from the desktop, but I think it is started in the
privileged session for services. The problem with running it within a
deskt
What's the answer? That CYGWIN sshd can not interact with the Windows
desktop?
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwi
Greetings, mhallnh!
> Has anyone been able to get the CYGWIN sssd service to interact with the
> Windows desktop?
> If yes could you please reply back with the details on how you got it to
> work.
Re-read the message you were replying to. It contains the answer.
--
With best reg
Has anyone been able to get the CYGWIN sssd service to interact with the
Windows desktop?
If yes could you please reply back with the details on how you got it to
work.
Thanks,
Mitch Hall
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
Problem reports: http
* plasma-desktop-5.8.9-1
* plasma-integration-5.8.9-1
* plasma-pa-5.8.9-1
* plasma-sdk-5.8.9-1
* plasma-workspace-5.8.9-1
* plasma-workspace-wallpapers-5.8.9-1
* systemsettings-5.8.9-1
* systemsettings-devel-5.8.9-1
This is an update to the latest 5.8 LTS release of the KDE Plasma Desktop:
https
up"?
In the former case, I'm not sure what, if anything, we can do to improve
matters.
In the latter, these are things we can fix, if we have the details of
which window is being hidden.
2) A 100MB file has appeared on my desktop. Is this part of the
installation? You will understan
Nicholas Joll writes:
> 2) A 100MB file has appeared on my desktop. Is this part of the
> installation? You will understand that I do not want to leave the folder
> there. What should I do, please?
Well that's because you asked the setup program to cache the downloaded
files
window. I wonder whether other users are likely to
encounter or have encountered that problem. (I have Cygwin . . actually,
I can't tell what version I've got. But I downloaded it just now from
your website.)
2) A 100MB file has appeared on my desktop. Is this part of the
installation
On 11/6/2017 4:48 AM, Yaakov Selkowitz wrote:
On 2017-11-03 12:05, Ken Brown wrote:
On 11/3/2017 9:11 AM, Ken Brown wrote:
In the meantime, I have another xpdf problem. After my update of the
ghostscript fonts, I get the following errors when starting xpdf:
Config Error: No display font for '
On 2017-11-03 12:05, Ken Brown wrote:
> On 11/3/2017 9:11 AM, Ken Brown wrote:
>> In the meantime, I have another xpdf problem. After my update of the
>> ghostscript fonts, I get the following errors when starting xpdf:
>>
>> Config Error: No display font for 'Courier'
>> Config Error: No display
On 11/3/2017 9:11 AM, Ken Brown wrote:
In the meantime, I have another xpdf problem. After my update of the
ghostscript fonts, I get the following errors when starting xpdf:
Config Error: No display font for 'Courier'
Config Error: No display font for 'Courier-Bold'
Config Error: No display fo
:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-kbrown'
I googled the message, but none of the solutions appeared to apply. Do
you know how to suppress this warning? I assume it results from the
fact that I'm not working in a desktop environment.
I don
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
> '/tmp/runtime-kbrown'
>
> I googled the message, but none of the solutions appeared to apply. Do
> you know how to suppress this warning? I assume it results from the
> fact that I'm not working in a deskt
f years and then use it continuously
>>>> without updates between those installations. I installed it on a new
>>>> laptop today, and I'm trying to work through issues.
>>>>
>>>> The current issue is running Emacs from the desktop.
>>>&g
x27;m trying to work through issues.
The current issue is running Emacs from the desktop.
I had a shortcut working for a long time that does the following:
-
C:\cygwin64\bin\run2.exe --display 127.0.0.1:0.0 /usr/local/bin/emacs.xml
-
Just '--display :0.0' is probabl
;m trying to work through issues.
>>
>> The current issue is running Emacs from the desktop.
>>
>> I had a shortcut working for a long time that does the following:
>> -
>> C:\cygwin64\bin\run2.exe --display 127.0.0.1:0.0 /usr/local/bin/emacs.xml
>&
On 11/1/2017 1:08 PM, David Karr wrote:
I install Cygwin every couple of years and then use it continuously
without updates between those installations. I installed it on a new
laptop today, and I'm trying to work through issues.
The current issue is running Emacs from the desktop.
I
I install Cygwin every couple of years and then use it continuously
without updates between those installations. I installed it on a new
laptop today, and I'm trying to work through issues.
The current issue is running Emacs from the desktop.
I had a shortcut working for a long time that
ogled the message, but none of the solutions appeared to apply. Do you
>>> know
>>> how to suppress this warning? I assume it results from the fact that I'm
>>> not
>>> working in a desktop environment.
>>
>> Normally set to /run/user/$(id -u)
:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kbrown'
I googled the message, but none of the solutions appeared to apply. Do you know
how to suppress this warning? I assume it results from the fact that I'm not
working in a desktop environment.
Normally set to /r
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kbrown'
>
> I googled the message, but none of the solutions appeared to apply. Do you
> know
> how to suppress this warning? I assume it results from the fact that I'm not
> working in a de
I googled the message, but none of the solutions appeared to apply. Do
you know how to suppress this warning? I assume it results from the
fact that I'm not working in a desktop environment.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http:/
On 10/27/2017 5:00 PM, Yaakov Selkowitz wrote:
---
xpdf.cygport | 4
1 file changed, 4 insertions(+)
Thanks!
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info
---
xpdf.cygport | 4
1 file changed, 4 insertions(+)
diff --git a/xpdf.cygport b/xpdf.cygport
index 7382054..dba7994 100644
--- a/xpdf.cygport
+++ b/xpdf.cygport
@@ -86,4 +86,8 @@ src_install() {
sed -e 's#/usr/local/share/xpdf#/usr/share/xpdf#g' -i ${D}/etc/xpdfrc
make_et
-kde4-5.8.8-1
* plasma-desktop-5.8.8-1
* plasma-integration-5.8.8-1
* plasma-pa-5.8.8-1
* plasma-sdk-5.8.8-1
* plasma-workspace-5.8.8-1
* plasma-workspace-wallpapers-5.8.8-1
* systemsettings-5.8.8-1
* systemsettings-devel-5.8.8-1
This is an update to the latest LTS release of the KDE Plasma Desktop
* mate-font-viewer-1.18.2-1
* mate-media-1.18.1-1
* mate-panel-1.18.4-1
* mate-screenshot-1.18.2-1
* mate-search-tool-1.18.2-1
* mate-session-manager-1.18.1-1
* mate-system-log-1.18.2-1
* mate-terminal-1.18.1-1
* pluma-1.18.2-1
The MATE Desktop Environment is the continuation of GNOME 2. It
-1.18.1-1
* mate-backgrounds-1.18.0-1
* mate-calc-1.18.0-1
* mate-common-1.18.0-1
* mate-control-center-1.18.1-1
* mate-desktop-1.18.0-1
* mate-dictionary-1.18.1-1
* mate-disk-usage-analyzer-1.18.1-1
* mate-font-viewer-1.18.1-1
* mate-icon-theme-1.18.2-1
* mate-indicator-applet-1.18.0-1
* mate-media
* oxygen-kde4-5.4.3-1
* plasma-desktop-5.8.5-1
* plasma-integration-5.8.5-1
* plasma-pa-5.8.5-1
* plasma-sdk-5.8.5-1
* plasma-workspace-5.8.5-1
* plasma-workspace-wallpapers-5.8.5-1
* systemsettings-5.8.5-1
This is an update to the latest LTS release of the KDE Plasma Desktop,
now based on Qt 5 and KDE
* libmatemixer-1.16.0-1
* libmateweather-1.16.0-1
* marco-1.16.0-1
* mate-applets-1.16.0-1
* mate-backgrounds-1.16.0-1
* mate-common-1.16.0-1
* mate-control-center-1.16.1-1
* mate-desktop-1.16.1-1
* mate-dictionary-1.16.0-1
* mate-disk-usage-analyzer-1.16.0-1
* mate-icon-theme-1.16.0-1
* mate-indicator-applet
Hi Jeff,
On Wed, Feb 1, 2017 at 6:22 AM, wrote:
> Jon, thanks for your suggestion. Using the -nocompositewm option
> fixed my problem. If you'd still like a screenshot, I can send one if
> the mailing list doesn't mind big attachments.
Instead of sending the screenshot to the mailing list, I'
win, I now find that all my X
windows (xterm, emacs, etc.) have color and font problems. Non-x
terminal windows are fine. Windows 7 is running as a VM on an esxi
hypervisor, so I view it remotely with Microsoft Remote Desktop. It
worked well on a previous cygwin release, but I don't have the
Remote Desktop. It
worked well on a previous cygwin release, but I don't have the exact
date when it changed. Also, I don't think the problem is with MRD
because I see it with VNC also.
Thanks for reporting this problem.
"color and font problems" is a bit vague. Can you
After a fairly recent update of cygwin, I now find that all my X
windows (xterm, emacs, etc.) have color and font problems. Non-x
terminal windows are fine. Windows 7 is running as a VM on an esxi
hypervisor, so I view it remotely with Microsoft Remote Desktop. It
worked well on a previous
* mate-terminal-1.14.1-1
* mate-themes-3.18.3-1
* mozo-1.14.1-1
* pluma-1.14.1-1
These are the latest updates to MATE Desktop 1.14. Each of the
mate-utils components have been split out into their own packages.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ
On Sep 1 07:14, Fjor wrote:
> Hi, Prabhakar,
>
> I upgraded my cygwin in XP to 2.6 and found that it doesn't work,
https://cygwin.com/ml/cygwin-announce/2016-08/msg00114.html, second
paragraph.
> Of course, when we have to upgrade packages again in the future, we must
> confirm that these thre
the future, we must
confirm that these three packages are marked "keep" to avoid them to be
modified by the installer during the upgrading process.
Regards,
Fjor
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/getting-cancelsynchronous-IO-error-when-starting
The following packages have been uploaded to the Cygwin distribution:
* desktop-file-utils-0.23-1
This package includes utilities for manipulating desktop files.
This is an update to the latest upstream release:
https://lists.freedesktop.org/archives/ftp-release/2016-June/000708.html
tcut and go the following error:
> > > "The procedure entry point cancelsynchronousio could not be located in
> > > the dynamic link libraryKERNEL32.DLL”.
> > Indeed, that Windows API function does not exist on XP:
> >
> >https://msdn.microsoft.com/libr
t be located in the
dynamic link libraryKERNEL32.DLL”.
Indeed, that Windows API function does not exist on XP:
https://msdn.microsoft.com/library/windows/desktop/aa363794.aspx
Does this not show that the Cygwin DLL is trying to call it?
I've tested mintty 2.4.2 on cygwin 2.5.2 on Win
; dynamic link libraryKERNEL32.DLL”.
Indeed, that Windows API function does not exist on XP:
https://msdn.microsoft.com/library/windows/desktop/aa363794.aspx
Does this not show that the Cygwin DLL is trying to call it?
$ objdump -x /bin/cygwin1.dll | grep CancelSync
[22724](sec 2)(f
1 - 100 of 300 matches
Mail list logo
