Opened 4 years ago
Closed 4 years ago
#1924 closed defect (fixed)
outer.startup.RouterAppManager: Client Desktop GUI START_FAILED Headless environment: not starting desktopgui!
Reported by: | anonymous maybe | Owned by: | zzz |
---|---|---|---|
Priority: | minor | Milestone: | 0.9.29 |
Component: | apps/console | Version: | 0.9.28 |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description (last modified by )
my i2p router installed inside debian standaloneVM on Qubes (which is like saying i2p inside Debian running inside virtualbox)
so yes it is actually Headless environment , but why the it is critical ? or why even matters for i2p to know or collect this information ?
- I2P Version and Running Environment
I2P version: 0.9.28-0-1ubuntu1 Java version: Oracle Corporation 1.7.0_111 (OpenJDK Runtime Environment 1.7.0_111-b01) Wrapper version: 3.5.25 Server version: 8.1.16.v20140903 Servlet version: Jasper JSP 2.1 Engine JSTL version: standard-taglib 1.2.0 Platform: Linux amd64 4.4.31-11.pvops.qubes.x86_64 Jcpuid version: 3 Processor: Haswell Core i3/i5/i7 model 60 (coreihwl) Jbigi: Locally optimized native BigInteger library loaded from file Jbigi version: 4 GMP version: 6.0.0 Encoding: UTF-8 Charset: UTF-8
- Critical Logs
1/7/17 7:09:45 PM CRIT [uterWatchdog] 2p.router.tasks.RouterWatchdog: Router appears hung, or there is severe network congestion. Watchdog starts barking! 1/7/17 7:49:45 AM CRIT [uter Console] outer.startup.RouterAppManager: Client Desktop GUI START_FAILED Headless environment: not starting desktopgui!
Subtickets
Change History (2)
comment:1 Changed 4 years ago by
Component: | apps/other → apps/console |
---|---|
Description: | modified (diff) |
Owner: | set to zzz |
Priority: | critical → minor |
Status: | new → accepted |
comment:2 Changed 4 years ago by
Milestone: | undecided → 0.9.29 |
---|---|
Resolution: | → fixed |
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
In 42b44d8741d898333a490de992a15394b5873b23 to be 0.9.28-4