﻿ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter
695,Black screen w/ intel integrated graphic,XOrg Configurator,9.1-RC3,,System Defect,,new,2013-02-15T04:44:52-08:00,2013-02-15T04:44:52-08:00,"On my laptop (Fujitsu Siemens Lifebook S7110) the defaults lead to a blank screen after X starts.  I have to enable the X configuration on the boot screen, then it's fine.  This is a blocker, because novice users will most probably not try that.",mjollnirpaul
696,keyboard selection shall be started by the installer,System Configuration,9.0-RELEASE,,System Defect,,new,2013-02-15T04:58:52-08:00,2013-02-15T04:58:52-08:00,"Not starting the keyboard selection can lead to an unusable system for novice users, because if the password contains letters differing from the default (US) to what the user sees on the keyboard (the language-specific type), she can not log in.  That's why it's a blocker.
",mjollnirpaul
699,Atheros WLAN driver not auto-detected,Misc,9.1-RC3,,System Enhancement,,new,2013-02-15T05:12:41-08:00,2013-02-15T05:12:41-08:00,"The Atheros AR242x/AR542x is not auto-detected.  Maybe an advanced user can fix that after installation, but for novice users this is a blocker.
In my case it means I have to try the installation w/ ethernet, try to enable WLAN once the system is properly installed, and if it does not work go back to Linux.  Not very attractive.",mjollnirpaul
716,System won't boot after security update April 2013,System Configuration,9.1-RELEASE,,System Enhancement,,new,2013-04-04T11:50:03-07:00,2013-04-08T13:31:14-07:00,"System update recommended a security update yesterday. My system would not boot this morning. I installed PCBSD 9.1 onto a different hard disk this morning, accepted all updates (including the security update), and the system wouldn't reboot (or, more precisely, reboots as described below). 
The BTX loader does its job, but the computer reboots at the end of the BTX loader sequence (displaying the power on screen and then booting again), suggesting that the kernel is no longer bootable. This happens quickly enough that I can't see what the last messages are.
The computer is an old Compaq model with a Sempron processor, and 1.25 GB memory. I am using the i386 version of PCBSD 9.1.",rrking
711,meta-pkg set emptied by some config script;  system-mgr shows no installed pkgs,System Configuration,9.1-RELEASE,,System Defect,,new,2013-03-07T08:26:33-08:00,2013-03-07T08:26:33-08:00,"but /usr/local/share/pcbsd/metaset has two subdirs, pcbd and trueos.
Both contain the relevant subdirs for the pkgs, and these in turn contain the file pkg-desc, pkg-icon.png, etc.

There's no subdir for warden (in the DBDIR), thus in warden the meta-pkg list for additions to a jail is empty.  This is logical.  But why does the system-mgr not shows the pkgs installed?

I consider this of priority: critcal, because one must have the impression that e.g. automatic security updates will not be applied: no pkgs, no updates needed.

This is only one example of bugs to prove my proposal on the pcbsd-dev mailing list.",mjollnirpaul
664,"Sound is Lost whilst playing Videos and Audio Media, auto fast forwarding occurs",Misc,9.1-RC1,,System Defect,,new,2012-10-02T13:45:45-07:00,2012-10-02T13:45:45-07:00,"I am running an '''Asrock N68-S UCC motherboard with NVIDIA Geforce 7025 Chipset'''.

Whilst playing any media e.g. youtube videos via firefox or audio via mplayer or Amarok. The sound abruptly stops after 3 mins or so and thereafter a constant buzz can be heard from the speakers until the application is closed. 

If any further attempts are made to play any audio/video, there is no sound AND the time lapse slider at the bottom of the youtube/amarok/mplayer fast forwards to the end of the media track without any sound being heard from the speakers.

If the initial sound crash occurs in say ''youtube'', then media playback via all software is effected i.e. ''amarok'' and ''mplayer'' will also play in fast forward (but without sound) 
'''after''' the youtube sound crash. 

A very strange bug which can be reproduced upon my 64 bit amd system after reboot with annoying reliability.",Dante77
667,Kernel Panic at Boot on Intel Mother Boards,System Configuration,9.1-RC1,,System Defect,,new,2012-10-07T13:18:44-07:00,2012-11-16T12:40:46-08:00,"When I try to boot either PC-BSD 9.0 stable or 9.1 RC1 after what seems to be an uneventful installation on either one of two Intel mother boards, the system panics at:
ZFS file system version 5
ZFS pool storage version 28
panic: no usable event timer found!
cpuid=0
KDB backtrace:#0  0xffffffff809205 at kdb_backtrace+0x66
#1  0xffffffff808ed55e at panic+0x1ce
#2  0xffffffff80c3baec at CPU_init_clocks_bst+0x3bc
#3  0xffffffff8054bcf7 at mi_startup+0x77
#4  0xffffffff802b4fec at btext+0x2c
uptime: 1 sec
Reboot....

In both cases, the install DVD loads and runs what seems to be flawlessly. 

The boards in question are:

Intel D945PSN - Bios:SN94510J.86A.0108.2008.0817.1811
Intel DP965LT(B) - Bios MQ96510J.86A.1761.2009.0326.0001

Both systems are 3.0 GHz Pentium D's; one has 2GB and one has 4GB. As a test, I successfully installed, booted, and ran FreeBSD 9.0 server and Puppy Linux 5.2 on both, so the hardware seems ok. I've tried multiple HD's, including a brand new 500GB SATA, and multiple install disks, including one distributed by PC-BSD. I updated the BIOS on the older board, but to no avail. Power supplies are new 500W units with 3-year warranties and different brands. The result was the same for both 9.0 stable and 9.1 RC1. The 9.0 install disk works well on a newer Socket 775 ASUS mobo, but I haven't tried 9.1 on that machine. ",wmichaelb
675,does not display correctly,XOrg Configurator,9.1-RC1,,System Defect,,new,2012-10-13T06:45:48-07:00,2012-11-08T22:22:44-08:00,"I tried to install PCBSD 9.1 RC2 on my lenovo y570 from the USBLITE image, and it worked fine (hung up for three minutes on boot, but pushed through), except for the fact that when I tried to boot it up, it made it to a screen featuring a fluxbox bar, and nothing else. it didn't respond when I right or left clicked, it just got these green streaks on it.",empathica
682,PCBSD9.1-x86-DVD.iso can not encrypt hard disk,System Configuration,9.1-RC3,,System Defect,,new,2012-12-18T17:39:41-08:00,2012-12-18T17:59:05-08:00,"PCBSD9.1-x86-DVD.iso
md5sum:ad7783c4b0673195d2c9d11cc5480593

-----------------------------------------
1,PCBSD9.1-x86-DVD.iso can not encrypt hard disk

2,PCBSD9.1-x86-DVD.iso ,wine-1.4.1 or wine-1.5.19 do not support chinese,while the PC-BSD 9.0 version is good on supporting chinese,

Thanks, 
",pcbsdunix
689,.xsession will display pass when adding user,System Configuration,9.0-RELEASE,,System Defect,,new,2013-01-13T05:25:46-08:00,2013-01-13T05:25:46-08:00,"Steps:
1. Add a user in Control Panel
2. Open .xsession-errors
3. Look for the line ""Case 0 was found!!!.........Name pass: Pass""
4. See the pass of the user added is displayed

Expected behavior:
Any pass should not be displayed

Pasted below are some of the lines together with the pass line in .xsession-errors
libpng warning: Duplicate iCCP chunk
starting submit() 
before username validation......... 
before full name validation......... 
before password validation......... 
after password validation......... 
""Case 0 was found!!!.........Name pass: Pass"" 
Before back->addUser 
Starting addUser  ""Name"" 
Done with crypt now........
",cabpa
693,VirtualBox metapackage doesn't install gnutls which prevents headless from working,Software Manager,9.0-RELEASE,,System Defect,,new,2013-02-14T23:28:18-08:00,2013-02-14T23:28:18-08:00,"{{{
[virtualbox@zinc ~]$ VBoxManage startvm openSUSE_12.2_x86 --type headless
Waiting for VM ""openSUSE_12.2_x86"" to power on...
VBoxManage: error: The virtual machine 'openSUSE_12.2_x86' has terminated unexpectedly during startup with exit code 1
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee 
[virtualbox@zinc ~]$ VBoxHeadless startvm openSUSE_12.2_x86                                                                                                                                               
VBoxHeadless: supR3HardenedMainGetTrustedMain: dlopen(""/usr/local/lib/virtualbox/VBoxHeadless.so"",) failed: Shared object ""libgnutls.so.47"" not found, required by ""libvncserver.so.0""
[virtualbox@zinc ~]$
}}}
After installing gnutls-2.12.18_1

{{{
[virtualbox@zinc ~]$ VBoxManage startvm openSUSE_12.2_x86 --type headless
Waiting for VM ""openSUSE_12.2_x86"" to power on...
VM ""openSUSE_12.2_x86"" has been successfully started.
[virtualbox@zinc ~]$
}}}

The VirtualBox metapackage needs to have gnutls as a dependency.
{{{
[virtualbox@zinc ~]$ ldd /usr/local/lib/virtualbox/VBoxHeadless.so
/usr/local/lib/virtualbox/VBoxHeadless.so:
        libvncserver.so.0 => /usr/local/lib/libvncserver.so.0 (0x80121d000)
        VBoxRT.so (0x801479000)
        VBoxXPCOM.so (0x80179a000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x801abd000)
        libm.so.5 => /lib/libm.so.5 (0x801dcd000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x801fee000)
        libc.so.7 => /lib/libc.so.7 (0x80081b000)
        libz.so.6 => /lib/libz.so.6 (0x8021fb000)
        libpng15.so.15 => /usr/local/lib/libpng15.so.15 (0x80240f000)
        libjpeg.so.11 => /usr/local/lib/libjpeg.so.11 (0x80263c000)
        libgnutls.so.47 => /usr/local/lib/libgnutls.so.47 (0x802873000)
        libthr.so.3 => /lib/libthr.so.3 (0x802b39000)
        libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x802d5c000)
        librt.so.1 => /usr/lib/librt.so.1 (0x803058000)
        libssl.so.6 => /usr/lib/libssl.so.6 (0x80325d000)
        libcrypto.so.6 => /lib/libcrypto.so.6 (0x8034b0000)
        libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x803853000)
        libcurl.so.6 => /usr/local/lib/libcurl.so.6 (0x803ba4000)
        libnettle.so.4 => /usr/local/lib/libnettle.so.4 (0x803dfd000)
        libgmp.so.10 => /usr/local/lib/libgmp.so.10 (0x804021000)
        libhogweed.so.2 => /usr/local/lib/libhogweed.so.2 (0x80428c000)
        libintl.so.9 => /usr/local/lib/libintl.so.9 (0x80449e000)
        libp11-kit.so.0 => /usr/local/lib/libp11-kit.so.0 (0x8046a8000)
}}}",jdmulloy
713,"Standby, Suspend, Power Off, Shutdown Problems",System Configuration,9.1-RELEASE,,System Defect,,new,2013-03-11T17:17:33-07:00,2013-03-11T17:17:33-07:00,"I am using PCBSD 9.1 (amd64) on my computer.  The hardware listed for my computer is CPU Intel(R) Xeon(R) CPU E31225.  I use Gnome or LXDE for my desktop and it's worked well.  When I tried using KDE for the desktop it froze and I couldn't close windows I opened.  In order to logout of KDE I had to turn off the power to the computer because nothing else worked.  When I check hardware compatibility in my PCBSD Control Panel everything has green checks.  I have the screen saver set and it works well.

The problem is I would like to use Standby and Suspend on my computer to save power.  Every time I enable Power Management in the Screen Saver Preferences and the computer goes into Standby, Suspend, Power Off, or Shutdown the screen goes black and the light on the monitor button changes from blue to orange.  The tower might keep running like it would when I'm using the system because I can hear it and it’s warm but the monitor is black and the light on the monitor button is orange.

When I try to use the computer again I either hit the space bar on the keyboard or push the power button on the tower.  No matter what I do the screen stays black and the monitor button stays orange.  I have to turn off the power to the computer, turn it back on, and let it boot before I can login and use the system.

When I want the computer to turn off and the tower stop running the only thing that works is to use Hibernate.  If I try to logout and click Shutdown the computer the screen goes black but it never completely goes off like it does when I use Hibernate.  I can Restart the system and restarting has never been a problem.

What can I do to fix the issues with Standby, Suspend, Power Off, and Shutdown?  I need to use these features but I can't rely on them.",Eternal
715,pc-mounttray and codepage,System Tool,9.1-RELEASE,,System Defect,,new,2013-04-03T00:29:30-07:00,2013-04-03T00:29:30-07:00,"I can't use pc-mounttray to mount usb flash with codepage ru_RU.UTF-8.
this program use standard command:
mount -t msdosfs -o large,-m=644,-M=777 /dev/da0s1 /media/<folder>
but for me need:
mount -t msdosfs -o large,-m=644,-M=777,-Lru_RU.UTF-8 /dev/da0s1 /media/<folder>
",erd
717,USB installation fails for language Japanese,System Configuration,9.0-RELEASE,,System Defect,,new,2013-05-08T04:02:21-07:00,2013-05-08T04:32:10-07:00,"Regardless of hardware, disk, size of partition, amount of RAM and CPU,
using installer in language Japanese fails for following releases:
PCBSD9.1-RELEASE-04-03-2013-x86-USBFULL.img,
PCBSD9.1-RELEASE-04-03-2013-x64-USBFULL.img,
PCBSD9.1-RELEASE-04-12-2013-x86-USBFULL.img,
PCBSD9.1-RELEASE-04-12-2013-x64-USBFULL.img.
I see no X11 screen in the first boot.  I can not find
/usr/home, symbolic link from /home to /usr/home, /etc/rc.conf.pcbsd,
rc.conf.pcbsd in the variable rc_conf_files in /etc/defaults/rc.conf,
/etc/pf.conf, /usr/local/etc/rc.d/pcbsdinit.  These are all missing
so that initialization process which should be done in the first boot will never be executed.  This phenomenon does not appear when I use the installer in language English.  Neither it happens for the release
PCBSD9.1-RELEASE-03-06-2013-x86-USBFULL.img.
Here I attach a sample of pc-sysinstall.log.
",NaomasaMaruyama
718,HTTP 403 Forbidden accessing pc-updatemanager mirror,PC-BSD Updater,9.1-RELEASE,,System Defect,,new,2013-05-08T07:21:53-07:00,2013-05-09T08:27:56-07:00,"I cannot access http://mirrors.isc.org/pub/pcbsd/system-updates/, resulting in the Update Manager error ""Failed to download"".  When I browse to the URL of one of the updates (e.g., http://mirrors.isc.org/pub/pcbsd/system-updates/noarch/warden-libsh-20130214.txz), I get a HTTP 403 Forbidden response from the web server.",xenophonf
719,Shutdown Options Corrupted by Using Virtual Terminal,System Configuration,9.1-RELEASE,,System Defect,,new,2013-05-08T10:29:28-07:00,2013-05-08T10:29:28-07:00,"I do not know what level of priority to set this to, so I will leave that to the moderators :-)

The summary of the problem is this. After starting the system and logging in as a regular user, if ANY user starts a virtual terminal, then the ability to ""politely"" shut the system down disappears and one must use the power switch or other inconvenient method.

I am running the 64-bit version of PC-BSD 9.1 in a VirtualBox Guest running on 64-bit Windows 7 Ultimate. The virtual computer is also configured to use ZFS RAIDZ with three hard drives but I have duplicated the problem with a single drive system. Below, are the steps I performed.

Start system and log in as regular, non-privileged user (using GNOME).

From main menu choose the following:
System -> Shut Down...

Choose System -> Shut Down...[[BR]]
Options now are Restart, Cancel Shut Down[[BR]]
Choose Cancel.

Start a virtual terminal by entering Ctrl+Alt+F2 (or F1, but I like F2 to reduce the ""noise"" from status messages).
Log in as regular user. You don't need to do anything here at the moment.

Switch back to GNOME by entering Ctrl+Alt+F9[[BR]]
From the main menu choose the following:[[BR]]
System -> Shutdown[[BR]]
Only option now is Cancel[[BR]]
Choose Cancel.

Return to virtual console by entering Ctrl+Alt+F2[[BR]]
Logout of this session (enter ""exit"")

Return to GNOME by entering Ctrl+Alt+F9[[BR]]
From main menu choose the following:[[BR]]
System -> Shutdown[[BR]]
The option still remains only Cancel.[[BR]]
Do nothing and let timer count down.

The system will not be shut down, but user will be logged out and returned to login screen (GDM?).

Log back in as the same unprivileged user.
From the main menu note that the System menu no longer has a Shut Down... option. Only Log out (name)... is available.

It is no longer possible to ""politely"" shut the system down. Either a terminal must be opened, ""su"" to root, and perform ""shutdown -h now"", logout as a regular user and log in as root and then shut down, or hit the power button on the computer.
",jon.duquesne
720,Permissions on pc-activedirectory.conf allow users to view domain admin password,System Configuration,9.1-RELEASE,,System Defect,,new,2013-05-09T09:22:56-07:00,2013-05-09T10:51:11-07:00,"/usr/local/etc/pc-activedirectory.conf should have permissions 0400, instead of 0444.  Otherwise, unprivileged users will be able to view the username and password of the account used to join the PC-BSD system to the domain.",xenophonf
707,ZFS-only system can not save crashdumps (no dumpdev),System Configuration,,,System Enhancement,,new,2013-02-21T09:16:04-08:00,2013-02-21T09:16:04-08:00,"PC-BSD 9.1 @ amd64
I set (or this was already default) dumpdev to AUTO in rc.conf, and enlarged the swap zvol to match the size of my RAM.  I've had several crashes :/ so I'd like to have crashdumps to append to bug reports.

I consider this ""major"" (or even ""critical"" or ""blocker"") 'cause like it is now one can not resolve other issues on a ZFS-only setup.

I remember crashdumps on a ZVOL were possible on OpenSolaris/Solaris Express and OpenIndiana, so ZFS should be able to handle that.  I didn't find a solution on the net, just some pages stating it's not possible to dump on a ZVOL on FreeBSD.
",mjollnirpaul
669,portjail /etc/rc.conf reverted on reboot,System Configuration,9.0-RELEASE,9.1,System Defect,,new,2012-10-09T10:52:52-07:00,2012-10-09T10:52:52-07:00,"On PCBSD-9.0 after a fresh portjail init and changing /etc/rc.conf after portjail console 
the changes are reverted after a system reboot or restart of portjail.",Nukama
684,PC-BSD 9.1 beta networking inoperative in VirtualBox,System Configuration,9.1-BETA1,9.1,System Defect,,new,2012-12-22T03:58:28-08:00,2013-01-13T15:32:10-08:00,"Ubuntu 12.04 host
VirtualBox 4.2.6 r82870
PC-BSD 9.1 beta guest from PCBSD9.1-X64-VBOX.vdi verified with md5sum

Unable to configure network so that it works. IP and NetMask are not configured in PC-BSD. Set up VirtualBox bridged network as directed in how-to's. Not familiar enough with BSD to set it up on command-line. GUI tools in PC-BSD show network as active, but is not functional. Network settings appear to be correct in PC-BSD GUI tools.

Posting from a Linux guest OS on the same VirtualBox system.

First time trying out PC-BSD, please forgive errors.",MoebusNet
714,VMWare mouse driver in ports failed in make,System Tool,9.1-RELEASE,9.1,System Defect,,new,2013-03-15T03:35:31-07:00,2013-03-15T03:35:31-07:00,"When I make the port x11-drivers/xf86-input-vmmouse in PCBSD 9.1 64-bit, I get errors, which I attached in this ticket. This port can make successfully in FreeBSD 9.1 64-bit.",null
683,Update mechanism should display remaining sizes,PC-BSD Updater,9.0-RELEASE,,System Defect,,new,2012-12-18T20:27:47-08:00,2012-12-18T20:27:47-08:00,The update mechanism should show the total quantity of data left to download.  It is confusing to see a package get to 100% and then go back to 0%.,eadler
688,Enable Custom DNS can be set with blank DNS,Network Manager,9.1-RC3,,System Enhancement,,new,2013-01-07T08:45:22-08:00,2013-02-10T13:08:23-08:00,"When you Enable Custom DNS in Network Manager, you can be set with blank DNS because the Save button is Enabled.
The Save button should be disabled when the DNS is blank.",cabpa
690,warden - add ability to have mounts per jails,System Tool,9.0-RELEASE,,System Enhancement,,new,2013-01-24T13:24:04-08:00,2013-01-24T13:24:04-08:00,"Just a small patch which adds the ability to mount files systems per jail. Drop a valid fstab file (named fstab) in the jail metadirectory and it will be mounted at jail start and unmounted and jail shutdown.

I uses this to mount nullfs filesystems that I want available to the jail. I added this as it is an option I am used to having using LXC on Linux",ermeaney
698,boot manager shall deal w/ int'l keyboards,Misc,9.1-RC3,,System Enhancement,,new,2013-02-15T05:05:20-08:00,2013-02-15T05:05:20-08:00,At least GRUB has an option to do that.  That's very useful.,mjollnirpaul
701,kernel modules could be loaded automagically,Misc,9.1-RC3,,System Enhancement,,new,2013-02-15T05:37:47-08:00,2013-02-15T05:37:47-08:00,"1. By default, the system starts many unneded modules, e.g. if I do not have encrypted drives, no mirrors, no ufs, etc., why are these modules loaded anyway?
2. Modules shall be loaded on-demand, when-needed automagically.
3. Is it a good idea to have an initial RAM-disk image containing the kernel modules and some logic to detect which modules to load like in Linux? ",mjollnirpaul
692,PC-BSD Enhancement for VMWARE Player,System Configuration,9.0-RELEASE,,System Enhancement,,new,2013-02-09T07:16:53-08:00,2013-02-09T07:16:53-08:00,"I like using VMWARE Player because it allows for directly opening the downloaded iso file when installing PC-BSD (very nice!).
Nothing is perfect however (yet) and final installation can have issues with screen resolution (post # 7 still applies)
http://forums.pcbsd.org/showthread.php?t=7887

Also VMWARE Tools do not install properly (see step 7) so a lot of extra work is needed to compile things.
http://www.rhyous.com/2012/05/09/installing-vmware-tools-on-freebsd-9-without-xorg/

Also VMWARE video driver does not get installed with VMWARE tools and more work is needed to get it
http://www.rhyous.com/2010/01/29/how-to-install-the-vmware-video-card-driver-on-a-freebsd-8-guest-virtual-machine/

I propose that everything needed to support VMWARE player gets figured out in advance and included in iso installation file and have some GUI widget available to enable VMWARE support once PC-BSD is installed. This type of enhancement can improve users PC-BSD experience a lot when installing on a virtual machine.

Thanks!

",jdwarren
702,Add short help to expand live USB filesystem,Misc,9.1-RC3,,System Enhancement,,new,2013-02-15T05:48:22-08:00,2013-02-15T05:48:22-08:00,"In the live system, add a short help when asking to expand the filesystem on the USB stick, telling the user what's it good for.  Like this:
""Expanding the FS to use the full size of your USB-Stick will enable you to install more applications and keep the data and configuration you created in the live system.""",mjollnirpaul
705,Qt apps shall respect desktop style settings,System Configuration,,,System Enhancement,,new,2013-02-19T04:54:36-08:00,2013-02-19T04:54:36-08:00,"The Qt style is set fixed to QtCurve.
(Partial) Fix: in qtconfig-qt4, set style to ""Desktop Settings (Default)"".  Unfortunately, the scrollbars are ugly and not like in KDE, but that's not very important.

This should be system-wide default, for new accounts, too, and I do not know how to do that, i.e. may be port comes w/ the wrong preset.",mjollnirpaul
709,Adjust date in filenames to have (sort alphabetical = sort by date),Misc,9.1-RELEASE,,System Enhancement,,new,2013-02-27T16:26:43-08:00,2013-02-27T16:26:43-08:00,"change:
PCBSD-9.1-RELEASE-02-26-2013-...
to:
PCBSD-9.1-RELEASE-2013-02-26-...

This should be a general policy when it comes to file names.",mjollnirpaul
687,gdm window manager selector not available,System Configuration,9.1-RC3,9.2,System Defect,,new,2012-12-30T21:07:46-08:00,2012-12-30T21:07:46-08:00,"Problem: gdm does not display window manager session selections with default PCBSD 9.1-RELEASE install.

Fix: comment out 'gdm_enable=""YES""' in rc.conf and insert 'kdm4_enable=""YES""'.

Description: I did a fulldisk install of PCBSD 9.1-RELEASE (amd64) from DVD this weekend on a Dell Inspiron 14z (N411z) laptop with an Intel Core i3-2350M CPU, 4GB RAM, 240 GB PNY Prevail Elite SSD, Dell BIOS (09/10/20112), Intel HD Graphics (1366x768 32-bit), and Intel chipset. I used all default settings with the following selections: filesystem is zfs with geli boot, desktop is Enlightenment, no other selections or packages.

After install the gdm login manager started Enlightenment and I started to test the system. Enlightenment ran slow and had a few hangs and crashes so I added KDE and WindowMaker from the PCBSD Control Panel/System Manager/System Packages tool. When I rebooted the gdm login manager did not display a method to select from alternate desktops and only logged in to KDE.

I commented out 'gdm_enable=""YES""' in rc.conf, rebooted and tried starting gdm, gdm-binary, xdm, and kdm from the command line. All would start KDE but did not have alternate desktop selections available. I tried copying the *.desktop files from /usr/local/share/xsessions/ directory to /usr/local/etc/gdm/Sessions/ and /usr/local/etc/dm/Sessions/ directories and retried starting the display managers (with multiple reboots in between) with the same effect - no alternate window manager selections and KDE started at login. I also tried some xinitrc edits with no luck. Then I tried kdm4 from the command line (I didn't think of it earlier) and I got a display manager GUI with a drop down for multiple window managers, including Enlightenment, KDE, and WindowMaker. All start successfully when selected.

I left gdm_enable=""YES"" commented out in rc.conf and inserted a kdm4_enable=""YES"" string and now my logins work correctly.

I have attached copies of my pc-sysinstall.log and my PCBSD Diagnostic Sheet from the sysmanager status tool.",b o b
670,skype won't start,PBI System,9.0-RELEASE,,System Defect,ken,new,2012-10-09T14:11:51-07:00,2012-11-05T10:04:39-08:00,"$ uname -a
FreeBSD pcbsd-1427 9.0-RELEASE FreeBSD 9.0-RELEASE #3: Tue Dec 27 21:59:00 UTC 2011     root@build9x64.pcbsd.org:/usr/obj/builds/i386/pcbsd-build90/fbsd-source/9.0/sys/GENERIC  i386

$ skype
ERROR: ld.so: object '/usr/lib/libv4l/v4l2convert.so' from LD_PRELOAD cannot be preloaded: ignored.
/usr/pbi/skype-i386/share/skype/skype: error while loading shared libraries: /usr/pbi/skype-i386/lib/libSM.so.6: ELF file OS ABI invalid
",adsfasdfadf
623,Sleep Mode Not Working with PCBSD,System Tool,9-SNAPSHOT,,System Defect,kris,new,2012-06-28T08:37:22-07:00,2012-06-28T08:37:22-07:00,"This suggestion was originally accepted from the forums from user Minghi.  Several users are reporting that they are unable to use sleep mode with PCBSD.  Users reported intel based hardware and nvidia based hardware having the problem.  I will assign this to you Kris per our conversation.  Please reference the forum post below for the original report from our user.

http://forums.pcbsd.org/showthread.php?p=97183&posted=1#post97183",joshms
638,init:: can't exec getty '/usr/libexec/getty' for port ...,System Configuration,9.1-BETA1,,System Defect,kris,new,2012-08-24T20:43:02-07:00,2012-09-25T10:25:59-07:00,"When I upgraded from 9.0 to the 9.1 beta I had the above problem.  I just upgraded from the latest beta to RC1.

While the box was applying package updates there was a kernel panic after a fair number of packages were installed.

I rebooted the box and what I get is the system mounts the root filesystem and I immediately get the 'getty' messages described above.  The system does not let me log in.

If I boot in to single-user mode I can mount the filesystems just fine, but when I exit single user mode I'm left at an Amnesiac login prompt - the system does not try and go multi-user.",harlan
677,PC-BSD 9.0 x86_64 failed to run on MacBook Pro,Installer,9.0-RELEASE,,System Defect,kris,new,2012-10-23T01:34:56-07:00,2012-10-23T01:34:56-07:00,"After installing the system on one of the slices on ada0, The Mac didn't recognize it from the computer and didn't show it on the screen. I've successfully installed and ran PCBSD9.0i386 though. Hope you guys can check this out.
",dannyniu
678,PC-BSD 9.1 RC2 Install using ZFS fails to boot,Installer,9.1-RC2,9.1,System Defect,kris,new,2012-10-29T21:59:39-07:00,2013-03-06T17:24:18-08:00,"Installing PCBSD9.1-RC2-x64-USBFULL.img with default install creates a system that does not boot after install. Changing the settings to NOT use ZFS, but UFS works.

My machine: Lenovo T420, 4GB RAM, 1TB hard drive.

The machine boots to the F1 - FreeBSD F6 PXE prompt ... goes to newline, sits there for what seems forever ... nothing else is going on activity-wise ... just a hang.",rhdinah
697,lnaguage selection shall propagate to keyboard type and vice versa; default keboard type,Installer,9.1-RC3,,System Enhancement,kris,new,2013-02-15T05:02:25-08:00,2013-02-15T05:02:25-08:00,"1. Whatever is first asked from the user (language/keyboard) shall propagate it's selection to the other initially.

2. The default type for non-english keyboards shall be 105-keys (Int'l); at least this is true for most german keyboards.",mjollnirpaul
700,language selection shall propagate to timezone,Installer,9.1-RC3,,System Enhancement,kris,new,2013-02-15T05:25:17-08:00,2013-02-15T05:28:47-08:00,"1. The language selection shall propagate to the timezone selection.
2. The timezones the user is most probably in shall be 1st on the list; is it a good idea to have 2 or even 3 lists: most propables, all named (Continent/City), all technical (UTC,UTC+1,...) and a selection in one list automatically updates the selection in the others.
3. The named (Continent/City) list could be divided into expandable sublists, so I can expand and collapse the continent.",mjollnirpaul
686,EasyPBI cannot clean up .chroot dataset if snapshots exist (PCBSD 9.1),PBI Creator,9.1-RC3,9.1,PBI Packaging Bug,kris,new,2012-12-29T16:33:56-08:00,2013-03-11T06:18:25-07:00,"I just used EasyPBI under PCBSD 9.1 (DVD x64 version) for the first time and stumbled across a quirk during ""zfs destroy"" after a build is successful.

I tweak my FreeBSD desktops to make zfs snapshots of all mounted zfs datasets every 15 minutes (and delete them every few hours). EasyPBI created a .chroot zfs dataset for its own use when I initiated ""Build PBI"". So now, while EasyPBI is doing its thing, my snapshot'ing script starts creating snapshots of the .chroot dataset every 15min.

When EasyPBI finishes building the local PBI, it trys to ""zfs destroy"" the .chroot dataset and fails. In particular, the log ends with:


{{{
	[...]
  Cleaning /usr/pbi/tetex-base-amd64.chroot
  cannot destroy 'tank1/usr/pbi/tetex-base-amd64.chroot': filesystem has children
  use '-r' to destroy the following datasets:
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0845
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0800
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0900
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0945
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0815
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0915
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0930
  tank1/usr/pbi/tetex-base-amd64.chroot@121230_0830
}}}


I suspect the solution is for EasyPBI to use ""zfs destroy -r"" rather than ""zfs destroy"", just to catch oddball cases like mine where the .chroot dataset ends up with children that really don't need to survive after the PBI build has succeeded.


",gja
