John Louis I, Count of Nassau-Wiesbaden-Idstein
John Louis I, Count of Nassau-Wiesbaden-Idstein (10 April 1567 – 10 June 1596) was the son of Count Balthasar of Nassau-Wiesbaden-Idstein and his wife Margaret of Isenburg-Bierstein. He succeeded his father in 1568 as Count of Nassau-Wiesbaden.
John Louis I, Count of Nassau-Wiesbaden-Idstein | |
---|---|
Born | 10 April 1567 |
Died | 10 June 1596 29) | (aged
Noble family | House of Nassau |
Spouse(s) | Maria of Nassau-Dillenburg |
Father | Balthasar, Count of Nassau-Wiesbaden-Idstein |
Mother | Margaret of Isenburg-Bierstein |
Marriage and issue
In 1588, John Louis married Maria of Nassau-Dillenburg, daughter of John VI, Count of Nassau-Dillenburg. They had the following children:
- Margaret (1589-1660), married in 1606 with Adolph of Bentheim, son of Arnold III, Count of Bentheim-Steinfurt-Tecklenburg-Limburg
- Anna Catherine (1590-1622), married in 1607 with Simon VII, Count of Lippe
- Juliana (1593-1605)
- John Philip (1595-1599), his successor with his brother John Louis II until his death
- John Louis II (1596-1605), his successor, the last male of Nassau-Wiesbaden-Idstein line
John Louis I, Count of Nassau-Wiesbaden-Idstein Born: 10 April 1567 10 June | ||
Preceded by Balthasar |
Count of Nassau-Wiesbaden-Idstein 1568-1596 |
Succeeded by John Louis II |
gollark: PotatOS's overrides printError if I remmemeemebnbebr right.
gollark: There are still two unpatched sandbox escape ones because *someone* (<@!235768051683950593>) won't tell me what they are, and PIR logging still isn't extensive enough to reveal them or give me a useful idea of what's going on.
gollark: In potatOS, a *ton* of vulnerabilities end up coming from process manager issues. By which I mean... two or so?
gollark: Generally, extensibility and (though this doesn't really apply within CC stuff which is basically single-user) security.
gollark: I feel like environment handling and task/process scheduling should be a separate system from your window manager.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.