Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bookmark not displayed if custom nickname is set #8563

Closed
cyberduck opened this issue Feb 8, 2015 · 4 comments
Closed

Bookmark not displayed if custom nickname is set #8563

cyberduck opened this issue Feb 8, 2015 · 4 comments
Labels
bug core fixed
Milestone
4.6.5

Comments

@cyberduck
Copy link
Collaborator

34b5299 created the issue

Steps to reproduce:

  • Create new bookmark
  • Exit Cyberduck
  • Run Cyberduck
    Now you can see the bookmark
  • Add nickname in the UI
  • Quit Cyberduck
  • Run Cyberduck
    Bookmark disapears
  • Quit Cyberduck
  • Edit bookmark file and delete Nickname
  • Run Cyberduck
    Bookmark appears again.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please let me know what nickname you have chosen and attach the file cyberduck.log in the application support directory.

@cyberduck
Copy link
Collaborator Author

34b5299 commented

I have added the log and two crash report file. I tried to reproduce it with a clean log file but I was not able, so I think this should be and upgrade problem. Hope the old log helps you to find out what the problem is.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
	at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:687)
	at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:557)
	at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1753)
	at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1426)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2754)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:125)
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:237)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:301)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
	at com.dd.plist.XMLPropertyListParser.parse(XMLPropertyListParser.java:129)
	at ch.cyberduck.core.serializer.impl.dd.PlistReader.parse(PlistReader.java:85)
	at ch.cyberduck.core.serializer.impl.dd.PlistReader.read(PlistReader.java:75)
	at ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:128)
	at cli.Ch.Cyberduck.Ui.Controller.MainController.<ApplicationDidFinishLaunching>b__b(Unknown Source)
	at cli.Ch.Cyberduck.Ui.Controller.AsyncDelegateBackgroundAction.run(Unknown Source)
	at ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
	at ch.cyberduck.core.AbstractController$BackgroundCallable.call(AbstractController.java:174)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:167)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:604)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:58)
	at java.lang.Thread.run(Thread.java:937)

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

In 59da75f.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug core fixed
Projects
None yet
Milestone
4.6.5
Development

No branches or pull requests
1 participant
@cyberduck