Can't access my Dev Alpha (A)

Hi,
I just rebooted my Dev Alpha and it says "Thanks for participating" and I can't do anything but to turn it off.
How to get access to it again?
Thanks
P.S. I'm on Windows XP
Solved!
Go to Solution.

The Dev Alpha A is no longer officially supported as of 10.1.0.1485. You can try downloading newer builds on to the divice from here:https://developer.blackberry.com/blackberry10devalpha/devalpha_update.html
But it is NOT supported.
Hope this was helpful. Happy Coding!
EK @echotown

Similar Messages

[SOLVED] can't access to /dev/ devices without superuser, using udev

Hello archers
Ive recently changed my distro from lubuntu to Arch64. In the way i've read many articles about trying to solve your problems in the wiki and such, the thing is, i made it this far without human help (exept some small talk with a friend) and i have encountered a mayor problem wich i can't solve by my own, i've been walking arround in circles and can't manage to get it working properly
$ uname -a
Linux Watch-Tower 3.2.11-1-ARCH #1 SMP PREEMPT Thu Mar 15 09:19:02 CET 2012 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ AuthenticAMD GNU/Linux
what i want to do:
- start PC
- insert pendrive/CD/DVD
- system will automatically mount the storage device
- be able to access it from PCmanFM (wich i've installed) without being r00t or superuser
- be able to unmount the storage device with a right click and "remove device" or such...
what i can do:
- insert a CD/DVD/USB-PENDRIVE and look at right column of PCmanFM to see it mounted (system will automatically mount the storage device)
- access the CD/DVD/USB-PENDRIVE files only if i use "sudo pcmanfm" and enter password first
- unmount only being a superuser or r00t
i hope i made myself clear. I've tryed to follow the wiki about udev and PCmanFM automount as regular user but if i add
exec ck-launch-session dbus-launch openbox-session
to my .xinitrc or to my slim.conf i get an error from SLiM that doesn't let me log in "slim failed to execute login command".
The only way that i can start openbox is by removing ck-launch-session of .xinitrc and/or slim.conf
i will post my confs in order to help others to understand what's happening what i don't for lack of experience and knowledge
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# See 'man 5 rc.conf' for more details
# LOCALIZATION
HARDWARECLOCK=""
TIMEZONE="America/Argentina/Buenos_Aires"
KEYMAP="es"
CONSOLEFONT="161"
CONSOLEMAP=
LOCALE=es_AR-UTF.8
DAEMON_LOCALE="yes"
USECOLOR="yes"
# HARDWARE
MOD_AUTOLOAD="yes"
MODULES=()
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"
# NETWORKING
HOSTNAME=Watch-Tower
interface=eth0
address=
netmask=
broadcast=
gateway=
NETWORK_PERSIST="no"
# DAEMONS
DAEMONS=(@udev @syslog-ng @network @dbus @crond)
.xinitrc:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
# exec ck-launch-session dbus-launch openbox-session
exec openbox-session
slim.conf:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
#login_cmd /bin/bash -login ~/.xinitrc %session
login_cmd /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user nicolas
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login yes
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme archlinux-simplyblack
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
hope someone has the answer out there, and is ready to share it,
thanks in advance.
Last edited by r@fitiiixxx (2012-03-21 07:19:32)

berbae wrote:
ck-launch-session is part of the consolekit package; is it installed on your machine?
And what do you have in the /etc/X11/xinit/xinitrc.d directory?
Also start your GUI and post, using code tags, the ouput of
ps -efww
You should also remember that there are log files to consult (in /var/log) to search for causes of problems...
I don't have LXDE, sorry for not telling you that before, just plain OpenBox wm. No DE in my machine. :S
$ sudo pacman -Ss consolekit
extra/consolekit 0.4.5-2 [installed]
A framework for defining and tracking users, login sessions, and seats
[nicolas@Watch-Tower xinitrc.d]$ ls
30-dbus 40-libcanberra-gtk-module pulseaudio xdg-user-dirs
what logs should i be looking for?
[nicolas@Watch-Tower log]$ ls
ConsoleKit crond.log.2 faillog slim.log.1.gz
Xorg.0.log daemon.log kernel.log syslog.log
Xorg.0.log.old daemon.log.1 kernel.log.1 syslog.log.1
Xorg.1.log daemon.log.2 kernel.log.2 syslog.log.2
auth.log dmesg.log lastlog user.log
auth.log.1 errors.log messages.log user.log.1
auth.log.2 errors.log.1 messages.log.1 user.log.2
boot errors.log.2 messages.log.2 wtmp
btmp everything.log old wtmp.1
crond.log everything.log.1 pacman.log
crond.log.1 everything.log.2 slim.log
ps -efww:
root 7 2 0 12:44 ? 00:00:00 [watchdog/0]
root 8 2 0 12:44 ? 00:00:00 [migration/1]
root 10 2 0 12:44 ? 00:00:00 [ksoftirqd/1]
root 11 2 0 12:44 ? 00:00:00 [kworker/0:1]
root 12 2 0 12:44 ? 00:00:00 [watchdog/1]
root 13 2 0 12:44 ? 00:00:00 [cpuset]
root 14 2 0 12:44 ? 00:00:00 [khelper]
root 15 2 0 12:44 ? 00:00:00 [kdevtmpfs]
root 16 2 0 12:44 ? 00:00:00 [netns]
root 17 2 0 12:44 ? 00:00:00 [sync_supers]
root 18 2 0 12:44 ? 00:00:00 [bdi-default]
root 19 2 0 12:44 ? 00:00:00 [kblockd]
root 40 2 0 12:44 ? 00:00:00 [khungtaskd]
root 41 2 0 12:44 ? 00:00:00 [kswapd0]
root 42 2 0 12:44 ? 00:00:00 [ksmd]
root 43 2 0 12:44 ? 00:00:00 [khugepaged]
root 44 2 0 12:44 ? 00:00:00 [fsnotify_mark]
root 45 2 0 12:44 ? 00:00:00 [crypto]
root 47 2 0 12:44 ? 00:00:00 [kthrotld]
root 89 2 0 12:44 ? 00:00:00 [ata_sff]
root 90 2 0 12:44 ? 00:00:00 [khubd]
root 95 2 0 12:44 ? 00:00:00 [scsi_eh_0]
root 96 2 0 12:44 ? 00:00:00 [scsi_eh_1]
root 99 2 0 12:44 ? 00:00:00 [kworker/u:2]
root 100 2 0 12:44 ? 00:00:00 [scsi_eh_2]
root 101 2 0 12:44 ? 00:00:00 [scsi_eh_3]
root 102 2 0 12:44 ? 00:00:00 [kworker/u:3]
root 109 2 0 12:44 ? 00:00:00 [kworker/0:2]
root 120 2 0 12:44 ? 00:00:00 [jbd2/sda3-8]
root 121 2 0 12:44 ? 00:00:00 [ext4-dio-unwrit]
root 170 1 0 12:44 ? 00:00:00 /lib/udev/udevd --daemon
root 207 170 0 12:44 ? 00:00:00 /lib/udev/udevd --daemon
root 208 170 0 12:44 ? 00:00:00 /lib/udev/udevd --daemon
root 210 2 0 12:44 ? 00:00:00 [edac-poller]
root 213 2 0 12:44 ? 00:00:00 [kpsmoused]
root 214 2 0 12:44 ? 00:00:00 [kworker/1:3]
root 223 2 0 12:44 ? 00:00:00 [hd-audio1]
root 248 2 0 12:44 ? 00:00:00 [ext4-dio-unwrit]
root 249 2 0 12:44 ? 00:00:00 [jbd2/sda4-8]
root 250 2 0 12:44 ? 00:00:00 [ext4-dio-unwrit]
root 286 2 0 12:44 ? 00:00:00 [flush-8:0]
dbus 551 1 0 12:44 ? 00:00:00 /usr/bin/dbus-daemon --system
root 553 1 0 12:44 ? 00:00:00 supervising syslog-ng
root 554 553 0 12:44 ? 00:00:00 /usr/sbin/syslog-ng
root 555 1 0 12:44 ? 00:00:00 /usr/sbin/NetworkManager
root 562 1 0 12:44 ? 00:00:00 /usr/lib/polkit-1/polkitd --no-debug
root 567 1 0 12:44 ? 00:00:00 /usr/sbin/crond
root 576 555 0 12:44 ? 00:00:00 /sbin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action eth0
root 579 1 0 12:44 tty1 00:00:00 /sbin/agetty -8 -s 38400 tty1 linux
root 580 1 0 12:44 tty2 00:00:00 /sbin/agetty -8 -s 38400 tty2 linux
root 581 1 0 12:44 tty3 00:00:00 /sbin/agetty -8 -s 38400 tty3 linux
root 582 1 0 12:44 tty4 00:00:00 /sbin/agetty -8 -s 38400 tty4 linux
root 583 1 0 12:44 tty5 00:00:00 /sbin/agetty -8 -s 38400 tty5 linux
root 584 1 0 12:44 tty6 00:00:00 /sbin/agetty -8 -s 38400 tty6 linux
root 585 1 0 12:44 ? 00:00:00 /usr/bin/slim
root 587 585 1 12:44 tty7 00:00:21 /usr/bin/X -nolisten tcp vt07 -auth /var/run/slim.auth
root 591 1 0 12:44 ? 00:00:00 /usr/sbin/console-kit-daemon --no-daemon
nicolas 664 585 0 12:44 ? 00:00:00 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
nicolas 676 1 0 12:44 ? 00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
nicolas 677 1 0 12:44 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
nicolas 682 1 0 12:44 ? 00:00:00 /usr/bin/pulseaudio --start
rtkit 684 1 0 12:44 ? 00:00:00 /usr/lib/rtkit-daemon
nicolas 692 682 0 12:44 ? 00:00:00 /usr/lib/pulse/gconf-helper
nicolas 694 1 0 12:44 ? 00:00:00 /usr/lib/GConf/gconfd-2
nicolas 701 664 0 12:44 ? 00:00:00 /bin/sh /usr/lib/openbox/openbox-autostart OPENBOX
nicolas 707 701 0 12:44 ? 00:00:00 sh /home/nicolas/.config/openbox/autostart
nicolas 710 707 0 12:44 ? 00:00:01 wbar --bpress --above-desk --vbar --pos right --isize 47 --nanim 3
nicolas 714 707 0 12:44 ? 00:00:00 tint2
nicolas 715 707 0 12:44 ? 00:00:00 sh /home/nicolas/.config/openbox/autostart
nicolas 722 715 0 12:45 ? 00:00:01 wbar --bpress --above-desk --vbar --pos right --isize 47 --nanim 3
nicolas 726 1 0 12:45 ? 00:00:00 /usr/lib/gvfs/gvfsd
nicolas 732 1 0 12:45 ? 00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/nicolas/.gvfs
nicolas 738 1 0 12:45 ? 00:00:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor
root 740 1 0 12:45 ? 00:00:00 /usr/lib/udisks/udisks-daemon
root 741 740 0 12:45 ? 00:00:00 udisks-daemon: not polling any devices
nicolas 746 1 0 12:45 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
nicolas 748 1 0 12:45 ? 00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
nicolas 762 1 0 12:46 ? 00:00:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0
nicolas 823 710 1 12:47 ? 00:00:18 midori
nicolas 829 1 0 12:47 ? 00:00:00 /usr/lib/gvfs/gvfsd-metadata
root 922 2 0 12:49 ? 00:00:00 [kworker/1:0]
root 930 2 0 12:54 ? 00:00:00 [kworker/1:1]
nicolas 951 664 0 13:00 ? 00:00:00 pcmanfm
nicolas 988 1 0 13:01 ? 00:00:00 leafpad /home/nicolas/.bash_history
nicolas 1029 664 0 13:03 ? 00:00:00 xterm -u8
nicolas 1030 1029 0 13:03 pts/0 00:00:00 bash
nicolas 1031 1030 0 13:03 pts/0 00:00:00 ps -efww
this is without ck-launch-session & dbus-launch!, if not, i wouldn't be posting this here...

Can't access maemo dev tools site

http://snag.gy/NvmrH.jpg
**bleep**?!

What are you searching for?http://maemo.org/development/
Happy to have helped forum in a small way with a Support Ratio = 37.0

Upgrade dev alpha to bb os10

hi, recently i acquired my z10 with the bb os10 software. However, there is a problem with the BBM as it can't connect to server. Then i use the autoloader for bb dev alpha and the bbm works. Now i want to revert back to bb os10 for the official release, is that possible? because i can't access my media features and most features went missing. Please help me with this problems.

The BBM server issues from the past 24 hours should be remedied by now, and you should have no problems.
If they persist, you should call your mobile provider and have this issue escalated to RIM's technical support.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

How can I access an unsupported usb device that's seen by system profiler

is there a way to access an unsupported usb device? my parents bought my daughter a cheap and easy to use digital camera and I am looking for a way to access the photos. the camera's manual mentions that there is no mac driver and there are no plans to develop one. I plug it in anyways in the event the system / Iphoto recognizes this, But I get nothing on the desktop as in a generic disk image icon. I open system profiler and My G4 knows the camera is plugged in. If this interface between the two is recognized how can I access the camera?
does a driver have to be written to allow access? I saw a usb dev kit on version tracker but I have no clue as to how to write a driver. I could get a flash card reader but I was hoping that there may be some back door or an app somewhere to allow me to get the photos off the camera.
thanks!!!

Hi, Israel.
You wrote: " I plug it in anyways in the event the system / Iphoto recognizes this"See if Image Capture recognizes the camera. Launch Image Capture, which is in the Macintosh HD > Applications folder.
Otherwise, you're probably going to have to go the route of using a card reader. While the connection may be USB, they may be using some non-standard implementation that requires a driver.
Writing drivers is not something you'd want to even attempt since you didn't create the hardware!
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Disk utility can't repair but can't access the HD to back-up files?

I'm relatively new to MACs and have a 2TB Seagate with a good portion of our family pics on it. I opened the Disk Utility and attempted to repair the HD but get the message:
"Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files."
Here's where I'm stumped...I can't actually access the disk to back it up. At one point I was able to open the disk and see the files so I went and bought another HD to back it all up....but now I can't access it. I've found a few threads discussing using recovery software but the data isn't that important. I was using the HD as my Time Machine BU so I'm more nervous about re-formatting it and trusting it with my data again. Should I bother even reformatting it or just toss the thing?

You might try a force mount...
Launch/Utilities/Terminal and enter this command at the prompt
diskutil list
Press return. If it sees the disk, note the number of the disk (far left column) you want to mount.
Then, enter this command
mount /dev/(number of disk)
Put in the number no parenthesis.
Press return.
If you're able to mount copy off the data you need. Even if you can mount it, wouldn't I trust the disk again.
Try Drive Genius in demo mode to run a surface scan and see if there are any bad blocks.

User can't access camera anymore, root still can [SOLVED]

since the last udev update, i can't access my camera anymore as user. gtkam gives this error:
An error occurred in the io-library ('Could not find the requested device on the USB port'): Could not find USB device (class 0x6, subclass 0x1, protocol 0x1). Make sure this device is connected to the computer.
the camera is a canon A75, vendor 04a9, product ID 305b. lsusb says it's connected to Bus 001 Device 011. i added that info to a custom 010.udev.rules file, but i don't know where to add the USB info. :?: user is in the camera group, btw.
ACTION=="add", SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="305b", RUN+="/bin/chmod o-rwx $env{DEVICE}"
ACTION=="add", SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="305b", RUN+="/bin/chgrp users $env{DEVICE}"
ACTION=="add", SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="305b", RUN+="/bin/chmod g+rw $env{DEVICE}", OPTIONS="last_rule"
thanks for any help.
>>edit: turns out root can't access the photos, either. the camera is detected and the photos load and show up in gtkam, but when i try to save them i get an error, e.g., "Problem getting 'IMG_0332.JPG' from folder '/store_00010001/DCIM/103CANON'." wtf? :?:
>>edit2: okay, i got it by adding
SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="305b", GROUP:="camera"
to a 00.gphoto.udev.rules file and restarting udev (i never noticed b4, but no script? i had to kill udevd and do /usr/sbin/udevd -d).
is that just a kluge fix though? i don't know anything about udev to know if that's the best way to do it, or if there's a better, more "correct" way. i just want to be able to access the camera from now on without having to change rules or mess around with udev anymore (i thought the point of udev was to have transparency to the user? ). thanks.
>> edit again: i love having conversations with myself.
okay, i didn't even notice the gphoto.rules file bfore, but i just added the information for my camera to the file, restarted udev, and it seems to work. if the maintainer wants to add the info for canon A75 to the file, the line is:
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="305b", GROUP="camera"

lanrat wrote:
Nice conversation :-)
If your camera isn't already in gphoto.rules you should report it to package maintainer (feature request) and/or gphoto devs.
I wouldn't modify standard gphoto.rules. I'd rather put this rule in /etc/udev/rules.d/00.udev.rules:
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="305b", GROUP:="camera"
to avoid overwriting after next update.
For restarting udev there is /etc/start_udev (or udev_start or something like this - I can't remember it :-))
thanks, it is /etc/start_udev - i was looking in /etc/rc.d.
i moved it back to 00.gphoto.rules so it won't get overwritten.
now that it's verified working in the standard rules, i'll make a report to the devs to add the cam there.
is your method for doing this in the wiki? i pretty much only figured out how to do it by reading your posts. if you have time, i think it would be a great wiki item. 8)

Can't access my windows dashboard

Hello,
Since few days i can't access my windows store dashboard but can access windows phone dashboard. Is anyone facing such problem? Any solution?
-Janak

Hello Janaks,
Are you still experiencing issues with signing into your developer dashboard?
If so, please try using IE11 InPrivate Browsing. If that still doesn't work please open a support ticket with:
Dev Center Support.
-Miles
Windows and Windows Phone Dev Center Support
Send us your feedback about the Windows Platform

Need file manager for dev alpha b

can some one give me link to best file manager for my dev alpha b device,as i didnt got it installed from default os

Try this:
Files & Folders, the unified file & cloud manager for PlayBook and BB10 with SkyDrive, SugarSync, Box, Dropbox, Google Drive, Google Docs. Free 3-day trial! - Jon Webb - Innovatology - Utrecht, Netherlands

Q10 10.2.1 OS on a Dev Alpha C?

Hello,
I would like to use the "full" 10.2.1 OS release of the Q10 on my Dev Alpha C and not just the Developer OS version of it.
Would the full Q10 OS work on a DAC?
If so, where can I download it?

Yes, two ways.
I would recommend using the Sachesi install process here.
Upgrading BB10 OS Using Sachesi
You can also use this:
Upgrading OS10 devices using Autoloader
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Camera problem in Dev Alpha C

Hi, my Dev Alpha C Smartphone has a problem with the camera, when I open the camera says that is not possible initiate the camera, and also can't capture screens. I swipe the smartphone and change the OS to different version, but nothing happen, the camera don't respond, is impossible initiate it.
Please can you tell me a solution?
Thanks a lot, Carlos Longarela.

Hi fotodng,
I have sent you a private message with the steps you need to take regarding your Dev Alpha device.
Let me know if you have any further questions.
Thanks!
-HMthePirate
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

[SOLVED]Can't access ntfs disk in thunar

I am trying to access files from a Windows disk. I mounted it (/dev/sda1) to ~/Windows but, when trying to open it in thunar, I get a permission denied error. How can I access my disk?
Last edited by Cube_Code (2013-09-02 07:31:20)

I did a:
usermod -aG storage my_username
and a:
lsblk -no UUID /dev/sda1
then recieved the output:
32B437F9B437BE63
and added this line to my /etc/fstab:
UUID=32B437F9B437BE63 /mnt/Windows ntfs
The problem persists. What have I done wrong?

Systemd access to /dev when logged in through ssh

I have user "X" logged in through SLIM and proper permissions to /dev devices are granted. When I log in as the same user "X" through SSH, I can't access /dev devices.
This prevents me from running emulators and sound applications through SSH, which is a PITA since the machine in question is a HTPC dedicated to running XBMC.
Any way to grant same permissions to SSH users as X sessions?
Last edited by arokh (2013-07-24 09:18:47)

I've been doing some digging on this, apparently display managers make sure the logged in session gets a "seat" from systemd. As long as you have a logged in X session, SSH sessions will also inherit the permissions from that seat.

Canon EOS camera recognized but system can't access to new photos

From some time I can't access to Canon EOS camera - DigiKam crashed when try to show camera flash content, konquerror shows empty space on the camera: pseudodevice.

Whow that's weird.
Assuming we're all talking about the same issue, as i said, i've tried an old kernel -3.9.3- and the problem didn't went away.
-EDIT
Anyway, confirmed.
3.10.5 works with the phone (didn't tested the camera)
Gozer ~ # mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 7, dev 3
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
^C
Gozer ~ # lsusb
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Ignore the "failed to open session" message, it is because (probably) the session was already opened by dolphin.
Last edited by kokoko3k (2013-08-07 14:23:18)

Blackberry 10 dev alpha. I am unable to syn this device to My laptop

Hi,
Can any one help me. I am new in BlackBerry development. I have BB10 dev alpha for testing of my apps. But i am unable to deployment or install any apps on BB10 dev alpha. could you please help me . how i can easly install apps on BB10 alpha dev.
If any reference, please help me where i can easly follow the deplayment process on BB10 dev aplha.
Regards.
Vikas Verma

1. Download DDPB Installer for windows (http://ddpb.dauden.vn/)
2. Download *.bar files at http://playbookbar.com
3. Turn on your BB10, Option-Security - Development Mode ON
3. Execute DDPD
4. Connect BB10 to PC, add the *.bar files and install it.
/..Omigo

Can't access my Dev Alpha (A)

Similar Messages

Maybe you are looking for