You are not logged in.
. . . with more great icons rather than tango...
Tango icons? There are no Tango icons in the default Devuan Xfce4 desktop theme. Not even installed on my computer.
@darry1966 . . . I'm not sure how much of the contamination is coming from upstream and how much is being introduced by Debian. As steelpillow mentioned . . . if the upstream source is clean (and init agnostic) we can work around blocks coming from Debian. But if upstream decides not to allow for other options, our work will indeed be much harder. The more traction that Devuan gains, the more leverage we'll have to expect upstream to support what we are doing.
I have already been banned once by golinux . . .
Really? From the time on jaromil's archived email (assuming UTC) - https://lists.dyne.org/lurker/message/2 … 43.en.html - I would have been sound asleep when it happened.
As to your sig etc. . . . it is an empty, adolescent gesture that accomplishes nothing of value but does create an environment that is equally toxic as the one that you are opposing. I keep hoping that maybe you'll grow up some day . . .
Maybe it needs gvfs to automount?
One more thing to try. I also have libgphoto2-port12 version 2.5.8-1~bpo8+1 installed. This was likely just a fluke because early on amprolla was merging bpo into the main repos. Took me a while to catch on to that so I do have some bpo mixed in that I ordinarily wouldn't have. But perhaps that's what gphoto2 needs? If all else fails, maybe a card reader would work?
I have no idea. Try without. Then the next option would be to log out/in. Then a reboot if all else fails. I'll keep my fingers crossed for you! Sorry it took me a few days to get around to pulling out the camera to get the info.
I have an old Canon Powershot (PTP) that wouldn't mount on Jessie. I can't remember how I got it working but it now automounts at gphoto2://[usb:001,056]/ with root permissions. A notification pops up and the directory appears in the Thunar side pane tree.
That directory contains these sub-directories,
DCIM - photos are here
MISC - empty
So you might want to install gphoto2 and see if it can find your camera at least. Some searching on the above might give you additional hints. No clues about your phone - don't have one.
@fungus . . . Do you know what Docker is?
@mcandre . . . Found this old thread on the dng mail list. There has been very little discussion of Docker over the years here - mostly lxc. But do search dng and the botbot logs for the freenode#devuan irc channel. You might find a kindred soul to work on Docker for Devuan.
Are you talking about https://gnuetertics.org? If so you should probably correct the spelling in the title.
OK. Where I can get sunxi image Devuan for my OrngPI ?
Is the one here not what you need?
Given that Pulse Audio was created by the same Rat responsible for systemd (vomit), should not we be using an ALSA based system for the management of Sound and associated devices?
This has been debated since the beginning of the fork. Since newer versions of Firefox require PA, our choice is to capitulate or devise a rock solid way to use apulse instead.
Should I file a Bug report for this at https://bugs.devuan.org/ ?
Sure, please do.
Thanks and welcome, viverna.
FOSSuser
Football is regarded by some as a religion, & therefore should be banned from the forum
I call for moderation!
More likely for your user info and footer . . .
Perhaps you'd like to change it?
Have you seen this? https://files.devuan.org/devuan_jessie/ … README.txt
Hadn't looked in a while because everything just works. But after looking at that tangled mess, I'm wondering how that can possibly be. Worst offender? Google hangouts! Avidemux was a close second. Just had to share . . .
. . . secondly I tend to prefer using the shift key or ctrl key to wake a sleeping compute . . .
Since I started to use the Ctrl key, there has not been one spontaneous reboot when waking up from suspend. So it was either that or possibly an upgrade around that time. I'll mark this as solved.
I do know they are working on the next release - ASCII - its named after a star.
No, not a star. It's the name of a minor planet in our solar system. ![]()
rsyslog is an issue - but there are two other loggers that work --(i did the something-ng one without an issue) and there is another workaround mentioned.
To clarify . . . from https://dev1galaxy.org/viewtopic.php?pid=4081#p4081
. . . you can install rsyslog from backports (or else replace it with syslog-ng or busybox-syslogd
Before you ask your question, search duckduckgo.com for any error messages you may have gotten because answers and/or documentation for Debian will often be the same for Devuan. Post here once you have confirmed that it's not an upstream issue,
If you have a question about Devuan, this user forum is a good place to start. But there are other resources available that might help you to find an answer even before you ask here or if your question here goes unanswered. Each of these resources has its pros and cons. Once you become more familiar with them, you'll know the best place to either find an answer or start a discussion about something new.
Devuan's irc channels always have the most current chatter about what's going on with Devuan. #devuan is logged at botbot and the search function will take you to conversations that go back to the very beginning of the fork. Irc is also where you'll most likely catch a developer to ask a specific technical question.
The DNG mail list was started before the fork was official. All the history is there as well as debates and sometimes lengthy technical discussions.
Finally, check the Devuan bugtracker to see if your issue has already been reported. If it has, respond with any additional information.
Please let me know if I've missed anything and I'll add it to this list.
Do you login with slim? Maybe try lightdm? Or possibly set the resolution in xorg.conf? I haven't had to do any of that in years but can remember when it was necessary.
Hope all goes well!
I surrender . . . Someone else with psychic powers and more patience that I is going to have to continue this adventure down a rabbit hole. Better yet I'm just going to lock this thread and put it out of its misery.
GNUser wrote:Here's a robust workaround for the time being
Its robustness was short-lived as that option to apt-file no longer exists.
More information as to why not would be helpful. Perhaps it was PEBKAC . . .
How do I attach - or otherwise provide access to - a file to a post. The file(s) in question are too large to include inline without totally cluttering up the message.
Thanks,
Attachments are not allowed on the forum. We hope to have something similar to http://paste.debian.net/ someday. But for now please chose a third party document posting site and link to it in your post.
again its debuan for the users or for "dev"'s only?
If you don't know the answer by now, you're not paying attention so I'm not going to repeat myself.
if documentation were put in right place . . .
This fragment is somewhat intelligible. Documentation is important. We all know that. It also needs to be written. It doesn't write itself. As to where is the right place? Well, that depends . . .
"babysit"'s dont ask so many to the "dev"'s ok, more respect to the users AGAIN!
I have no idea what you're trying to say here but I do know that you end by again wrongly judging and and insulting those of us working so hard on a project that you bitch about in nearly every post. Some gratitude for the tremendous effort it's taken to get this far would be appropriate. But then finding anything positive or remotely helpful in one of your posts is the last thing I'd ever expect. If you don't like it here and have such a low estimation of our efforts, please move on elsewhere . . .
golinux wrote:yeti wrote:The "Codename:" problem still is unanswered.
Trying to debmirror a dist with wrong codename results in mirroring the dist matching that codename...
That can't be correct!Have you filed a bug report? Or tried to contact a dev on #devuan or #devuan-dev?
Did the "or" part...
Yeah saw it in the backlog and just now connected it to you.
I can't remember if it was actually solved. (Too much to remember . . .) A bug report is a more permanent way of recording it. irc logs quickly fade into oblivion.