[Desktop-packages] [Bug 1972766] Re: Changing default mounting options causes root owner
However, you might point to them and they might point to you.
I hope it gets resolved.
I'm referring to two teams pointing at each other for the other to fix
it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1972766
Title:
Changing default mounting options causes root owner
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972766] Re: Changing default mounting options causes root owner
I am beyond my troubles with this issue and only compassionately posting
this issue to help others. With some careful thought, I will share this
issue with gnome nautilus team. It seems logical that one should be
able to right click on a drive located on the sidebar thinggy. or a
drive located in "Other locations" Right click, automount (obviously it
would be for the current user).
Perhaps a server would not like this mounted for everyone with sensitive
drives.. but then again.. you would not automount such sensitive drives.
However, you might point to them and they might point to you.
I hope it gets resolved. Auto-mount is essential for recent-file-lists to work
properly.
Ubuntu is quite stable and needs to focus on more usabliltiy issues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1972766
Title:
Changing default mounting options causes root owner
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972766] Re: Changing default mounting options causes root owner
The problem is, if you want a partition to be auto-mounted, you either must
edit the fstab or THE INSTRUCTIONS are to turn off the "default" mounting in
gnome disk utility and it will auto-mount. However, the auto-mounting is done
as system root and I don't have access to it. So I must google and google and
more google until I find that I put some settings like uuid=1000.
This is a big problem.
Why?
Well I setup my 22.04 with a full wipe, but kept my data partition.
My git was totally broken on my data partition and I thought it was ubuntu 22.04
But then with just git and ubuntu and vscode it worked.. so I installed the
rest of the apps and it broke (I also setup my data partition to auto-mount)
then I thought it was my proton vpn which was the only ppa
It took a long time to realize it was the auto-mount .. merely changing
defaults switch.
I had wiped my system 3 times before I figured this out.
Then I had to do a lot of googling to auto-mount for myself. It seems very
logical that I would want to use a drive that I setup as automount.
If the user is selecting auto-mount, why not automatically allow that user to
read access?
Instead it defaults to system.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1972766
Title:
Changing default mounting options causes root owner
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972766] Re: Changing default mounting options causes root owner
I think that there should also be checkboxes and options to help one
fill in the options line. Gui to select icon too. There is a reason
for GUI.. and it is not really being used.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1972766
Title:
Changing default mounting options causes root owner
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972766] [NEW] Changing default mounting options causes root owner
Public bug reported:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings. This
hard to research "mystery setting" is not acceptable for a GUI mounting tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
** Affects: gnome-disk-utility (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "fixed data partition settings"
https://bugs.launchpad.net/bugs/1972766/+attachment/5588085/+files/Screenshot%20from%202022-05-10%2012-01-54.png
** Description changed:
- If I change the default mounting options in Gnome Disk Utility the owner
- is root. This threw me for a loop when all of my git repos were not
- working. I thought it was an ubuntu 22.04 problem or a ppa.
+ Ubuntu 22.04
+ If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
- Control:
+ **Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
-
- Cause the bug.
+ **Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
-
- Fix For The Problem:
+ **Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1972766
Title:
Changing default mounting options causes root owner
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 237967] Re: control-q should quit
I read up on this one on the link provided. If Ctrl q is not allocated, it should be easy to close the current version. Surely you have a linux build. It is very standard to have ctrl Q not ctrl W -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/237967 Title: control-q should quit Status in Evince: Won't Fix Status in evince package in Ubuntu: Won't Fix Bug description: Binary package hint: evince I've got evince version 2.22.2-ubuntu1 It's lacking the standard "quit" option in the file menu, and ^q doesn't quit. ProblemType: Bug Architecture: i386 Date: Fri Jun 6 14:06:12 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince Package: evince 2.22.2-0ubuntu1 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/zsh PATH=/home/username/.dtach/bin:/home/username/bin:/home/username/software/virt/bin:/home/username/software/virt/sbin/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=C SourcePackage: evince Uname: Linux 2.6.24-18-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/237967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 237967] Re: control-q should quit
I read up on this one on the link provided. If Ctrl q is not allocated, it should be easy to close the current version. Surely you have a linux build. It is very standard to have ctrl Q not ctrl W -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/237967 Title: control-q should quit Status in Evince: Won't Fix Status in evince package in Ubuntu: Won't Fix Bug description: Binary package hint: evince I've got evince version 2.22.2-ubuntu1 It's lacking the standard "quit" option in the file menu, and ^q doesn't quit. ProblemType: Bug Architecture: i386 Date: Fri Jun 6 14:06:12 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince Package: evince 2.22.2-0ubuntu1 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/zsh PATH=/home/username/.dtach/bin:/home/username/bin:/home/username/software/virt/bin:/home/username/software/virt/sbin/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=C SourcePackage: evince Uname: Linux 2.6.24-18-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/237967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650281] Re: External Microphone of headset not working when plugged in
I hate to say this.. but "It works in Windows" (dual boot but nearly empty on Windows). Perhaps this is useful even though you do not like this phrase. The Acer website has a 250 megabite Realtek driver for windows. I have it downloaded but have not done anything with it. I am not sure if that will help. When I query my snd card it says Intel but I know it is Realtek. The hdmi is intel bhikkhusubhuti@Subhuntu:~$ lspci -v | grep -A7 -i "audio" 00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 311 Memory at 9141 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 21) (prog-if 00 [Normal decode]) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1650281 Title: External Microphone of headset not working when plugged in Status in alsa-driver package in Ubuntu: New Bug description: bhikkhusubhuti@Subhuntu:~$ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 bhikkhusubhuti@Subhuntu:~$ apt-cache policy alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages 100 /var/lib/dpkg/status What I EXPECT: I plug in a working headset. The internal mic should be muted and speakers muted. The headset and mic should work . WHAT HAPPENS: The headphones work but the microphone does not work. The internal microphone (which gives me static)... still works even though it should be muted. (another problem? I have static in my internal microphone and therefore try to fix this with an external plug in mic) Perhaps there is a quick fix for hdajackretask advanced mode. I tried setting pins 18 and 19 like the youtube video but nothing worked. I can mute the internal mic through this program though. Pulse Audio has been modified to not do autostart and I start it manually (to make hdajackretask allow changes. Yes I start it and the bug still exists.. (it existed before I modified it to not repeatedly autoload). Note: Without pulseaudio, I have no sound devices listed (this is new to me) maybe a gnome thing which I am new to from lubuntu and mate previously. I tried irc #ubuntu and installed pulse volume control.. nope I tried ask ubuntu. lanchpad.net had outdated stuff that I am not clear on. My computer is Acer c1yf. Previously I opted for a shared bug report, but noticed it is different and something could be fixed through alsamixer. I was not able to get it to work nor understood what he did anyway. I played with Gnome alsa mixer, hdaJackretast (as youtube video says) and even the conf file but could not get anything to work. I am on the mainline build 4.9 and latest 1.15 BIOS for acer 131t r3 downlaoded a few days ago (which caused me boot problems to fix). I am up to speed to qualify for investigation so I wish some help. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.9.0-040900-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhikkhusubhuti 6668 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 15 20:09:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-05 (40 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd07/04/2016:svnAcer:pnAspireR3-131T:pvrV1.15:rvnAcer:rnAspireR3-131T:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire R3-131T dmi.product.version: V1.15 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-14T15:49:54.217020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/
[Desktop-packages] [Bug 1650281] [NEW] External Microphone of headset not working when plugged in
Public bug reported: bhikkhusubhuti@Subhuntu:~$ lsb_release -rd Description:Ubuntu 16.10 Release:16.10 bhikkhusubhuti@Subhuntu:~$ apt-cache policy alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages 100 /var/lib/dpkg/status What I EXPECT: I plug in a working headset. The internal mic should be muted and speakers muted. The headset and mic should work . WHAT HAPPENS: The headphones work but the microphone does not work. The internal microphone (which gives me static)... still works even though it should be muted. (another problem? I have static in my internal microphone and therefore try to fix this with an external plug in mic) Perhaps there is a quick fix for hdajackretask advanced mode. I tried setting pins 18 and 19 like the youtube video but nothing worked. I can mute the internal mic through this program though. Pulse Audio has been modified to not do autostart and I start it manually (to make hdajackretask allow changes. Yes I start it and the bug still exists.. (it existed before I modified it to not repeatedly autoload). Note: Without pulseaudio, I have no sound devices listed (this is new to me) maybe a gnome thing which I am new to from lubuntu and mate previously. I tried irc #ubuntu and installed pulse volume control.. nope I tried ask ubuntu. lanchpad.net had outdated stuff that I am not clear on. My computer is Acer c1yf. Previously I opted for a shared bug report, but noticed it is different and something could be fixed through alsamixer. I was not able to get it to work nor understood what he did anyway. I played with Gnome alsa mixer, hdaJackretast (as youtube video says) and even the conf file but could not get anything to work. I am on the mainline build 4.9 and latest 1.15 BIOS for acer 131t r3 downlaoded a few days ago (which caused me boot problems to fix). I am up to speed to qualify for investigation so I wish some help. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.9.0-040900-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhikkhusubhuti 6668 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 15 20:09:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-05 (40 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd07/04/2016:svnAcer:pnAspireR3-131T:pvrV1.15:rvnAcer:rnAspireR3-131T:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire R3-131T dmi.product.version: V1.15 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-14T15:49:54.217020 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1650281 Title: External Microphone of headset not working when plugged in Status in alsa-driver package in Ubuntu: New Bug description: bhikkhusubhuti@Subhuntu:~$ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 bhikkhusubhuti@Subhuntu:~$ apt-cache policy alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages 100 /var/lib/dpkg/status What I EXPECT: I plug in a working headset. The internal mic should be muted and speakers muted. The headset and mic should work . WHAT HAPPENS: The headphones work but the microphone does not work. The internal microphone (which gives me static)... still works even though it should be muted. (another problem? I have static in my internal microphone and therefore try to fix this with an external plug in mic) Perhaps there is a quick fix for hdajackretask advanced mode. I tried setting pins 18 and 19 like the youtube video but nothing worked. I can mute the internal mic through this program though. Pulse Audio has been modified to not do autostart and I sta
[Desktop-packages] [Bug 441502] Re: Front Audio Jacks Not Working
My computer has a realtek ALC255 according to hdaJackRetask but lscipi
command shows only Intel. The windows version has realtek drivers. I
am not sure if that is the problem. I have seemed to have read that
there are sub sound systems and sometimes it does not choose them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/441502
Title:
Front Audio Jacks Not Working
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu karmic (development branch)
Release: 9.10
alsa-base:
Installed: 1.0.20+dfsg-1ubuntu4
What is expected?
I should plug in my headset (microphone included) and be able to hear
and talk through any software, or at least restart such software if it
does not automagically detect and adjust immediately so it may use the
new configuration.
What happened instead?
The front jacks do not seem to be working. They did in ubuntu 9.04
(and only the ubuntu flavour, they did not in kubuntu 9.04) but not
there's no output.
Microphone works with configuration!
* The microphone is still configured in the same manner. I open `alsamixer`.
* In the [Playback] View which opens by default I adjust certain settings to:
"Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I".
"Front Mic Jack Mode" TO "Mic In"
* In the [Capture] View:
"Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing)
"Capture" is ENABLED and volume adjusted (Maxed out for testing)
Any other option is discardable in the front microphone jack configuration.
This makes the microphone work when it is plugged in the front jack. I have
not tested the back panel.
Headphone
I have not been able to configure the headphones yet, I'm not an alsa
or pulse-audio expert ;[
LSPCI important output:
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
Audio Controller
Notes:
No alsa global configuration was tampered with. Only alsamixer for
microphone configuration.
ProblemType: Bug
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: exodus 1440 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22'
Mixer name : 'IDT 92HD73E1X5'
Components : 'HDA:111d7676,80865002,00100202'
Controls : 47
Simple ctrls : 29
CheckboxCommand: alsa_record_playback
CheckboxTest: alsa_record_playback_alternates
Date: Sat Oct 3 11:23:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.20+dfsg-1ubuntu4
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: alsa-driver
Tags: checkbox-bug
Uname: Linux 2.6.31-11-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/441502/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 441502] Re: Front Audio Jacks Not Working
I loaded the 4.9 upstream and 1.15 BIOS from ACER. Bug still exists.. Please
let me know what to do next. My internal microphone has static and I want to
use a headset and then eventually a plug splitter of microphone and headphone.
The headphones work.
The microphone does not work
Both work fine in windows (sorry).
I have pauvolume control and it does not list a secondary input device.
I tried hdajackretask and it also did not seem to work.
According to what I know.. The internal microphone should be muted and the
external should work..
That happens to the headphones and speakers respectively when you plug it in.
Please advise. Maybe you can help me figure out the "advanced settings"
for hdajackretask and then it can go into the builds for the next rc.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/441502
Title:
Front Audio Jacks Not Working
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu karmic (development branch)
Release: 9.10
alsa-base:
Installed: 1.0.20+dfsg-1ubuntu4
What is expected?
I should plug in my headset (microphone included) and be able to hear
and talk through any software, or at least restart such software if it
does not automagically detect and adjust immediately so it may use the
new configuration.
What happened instead?
The front jacks do not seem to be working. They did in ubuntu 9.04
(and only the ubuntu flavour, they did not in kubuntu 9.04) but not
there's no output.
Microphone works with configuration!
* The microphone is still configured in the same manner. I open `alsamixer`.
* In the [Playback] View which opens by default I adjust certain settings to:
"Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I".
"Front Mic Jack Mode" TO "Mic In"
* In the [Capture] View:
"Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing)
"Capture" is ENABLED and volume adjusted (Maxed out for testing)
Any other option is discardable in the front microphone jack configuration.
This makes the microphone work when it is plugged in the front jack. I have
not tested the back panel.
Headphone
I have not been able to configure the headphones yet, I'm not an alsa
or pulse-audio expert ;[
LSPCI important output:
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
Audio Controller
Notes:
No alsa global configuration was tampered with. Only alsamixer for
microphone configuration.
ProblemType: Bug
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: exodus 1440 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22'
Mixer name : 'IDT 92HD73E1X5'
Components : 'HDA:111d7676,80865002,00100202'
Controls : 47
Simple ctrls : 29
CheckboxCommand: alsa_record_playback
CheckboxTest: alsa_record_playback_alternates
Date: Sat Oct 3 11:23:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.20+dfsg-1ubuntu4
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: alsa-driver
Tags: checkbox-bug
Uname: Linux 2.6.31-11-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/441502/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 441502] Re: Front Audio Jacks Not Working
I did not load the upstream yet.. but I installed the latest bios and it did
not seem to work. I also tried a program called hdajackretask. This did not
work according to the youtube.com video I watched to make the microphone work.
So I am left with a problem. It should mute the speakers and internal mic and
allow me to use plugged in headset. The internal mic is still active and the
plugged in mic (of the headset) does not work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/441502
Title:
Front Audio Jacks Not Working
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu karmic (development branch)
Release: 9.10
alsa-base:
Installed: 1.0.20+dfsg-1ubuntu4
What is expected?
I should plug in my headset (microphone included) and be able to hear
and talk through any software, or at least restart such software if it
does not automagically detect and adjust immediately so it may use the
new configuration.
What happened instead?
The front jacks do not seem to be working. They did in ubuntu 9.04
(and only the ubuntu flavour, they did not in kubuntu 9.04) but not
there's no output.
Microphone works with configuration!
* The microphone is still configured in the same manner. I open `alsamixer`.
* In the [Playback] View which opens by default I adjust certain settings to:
"Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I".
"Front Mic Jack Mode" TO "Mic In"
* In the [Capture] View:
"Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing)
"Capture" is ENABLED and volume adjusted (Maxed out for testing)
Any other option is discardable in the front microphone jack configuration.
This makes the microphone work when it is plugged in the front jack. I have
not tested the back panel.
Headphone
I have not been able to configure the headphones yet, I'm not an alsa
or pulse-audio expert ;[
LSPCI important output:
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
Audio Controller
Notes:
No alsa global configuration was tampered with. Only alsamixer for
microphone configuration.
ProblemType: Bug
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: exodus 1440 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22'
Mixer name : 'IDT 92HD73E1X5'
Components : 'HDA:111d7676,80865002,00100202'
Controls : 47
Simple ctrls : 29
CheckboxCommand: alsa_record_playback
CheckboxTest: alsa_record_playback_alternates
Date: Sat Oct 3 11:23:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.20+dfsg-1ubuntu4
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: alsa-driver
Tags: checkbox-bug
Uname: Linux 2.6.31-11-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/441502/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1007423] Re: ibus won't turn 'on' when in certain programs
I can confirm that this does not work in ubuntu mate 16.04 with a custom keyboard (see http://www.ubuntu4u.com/howtos/how-to-type-romanized-pali-and-sanskrit-in-ubuntu-12041210) It works in terminal only. Burmese seems to work. The preferences for that particular setting does not work. (no dialog shows up) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1007423 Title: ibus won't turn 'on' when in certain programs Status in ibus package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Won't Fix Status in libreoffice package in Fedora: Unknown Bug description: What I expect to happen: I can turn on and change and use input methods in ibus in any program. What really happens: When in gedit, ibus turns on fine and I can input in Japanese (anthy) and other languages e.g. Chinese pinyin. However, when using firefox, I can't get the input method to change to anthy or any other from "Input method Off" using my shortcut keys (Ctrl+Space). If I manually right click ibus icon in the tray and left click the input method (e.g. anthy), the first time, the bullet point changes to anthy AND "Input method Off", the second time it will change completely to anthy but sometimes it stays at "Input method Off". Even if the bullet point changes to anthy, I am not able to input in anthy at all. The first time I turned ibus 'on' to anthy in EiskaltDC++ it worked, however the following times it didn't work at all. When I restart ibus, and try to switch to anthy or another input using right-click on the ibus icon, I only see "No input window" where there should be input methods. However, when I switch to kate/gedit, I am able to use any other input method, and can switch input methods using keyboard shortcut or GUI click menu. After switching to another input method (e.g. anthy), I am able to switch to other input methods in apps that I can't use other input methods in (e.g. firefox) via the GUI click menu (but not keyboard shortcut). If I check "Share the same input method among all applications": -- and switch to anthy (or any other input method besides "Input method Off") in gedit, I am able to type using anthy in gedit, but when I switch programs to firefox for example, it won't work. I can see the anthy logo in the tray icon, and also in the anthy menu, but all the switch "input mode" "typing mode" "conversion mode" "dictionary" buttons will have disappeared, and only the anthy logo button (change ibus input) and "About the input method" button remain. -- I can't change the input method (using keyboard shortcut orc GUI click menu) in any application I can't type using other input methods. -- I can also no longer change input methods using the GUI click menu, but must use my shortcut (Alt-Shift_L), even in applications that I can input non-english in (i.e. gedit/kate). Sometimes the GUI click menu displaying input methods with current input method bullet pointed doesn't display correctly, even in apps that I can input non-english in (gedit/kate). I must right-click the tray icon again for it to refresh and display properly. For example, if I switch using the keyboard shortcut, the input method will have changed but the bullet point will still be on the previous input method, unless I right click the tray icon again. To 'input' other languages into firefox (or any other program), I must first type in gedit or kate and then copy the text over to firefox. I can't even type non-english languages in LibreOffice Writer! I'm running Kubuntu 12.04 amd64 with KDE 4.8.3 and IBus 1.4.1-3ubuntu1 (On i5-520M, 4GB, GT330M) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ibus 1.4.1-3ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jun 1 23:33:41 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) ProcEnviron: LANGUAGE=en_AU TERM=xterm LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1007423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538596] Re: touchpad stops on acer 131t
This bug is caused by the bios being in "advanced mode" Windows needs Advanced mode and installs a driver. The bios says, "you need this driver or it may not work" Perhaps this driver should be added to the kernal? I still think this is a bug, because people will install ubuntu and think this is a piece of junk (like I did, but I am more patient) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1538596 Title: touchpad stops on acer 131t Status in unity-control-center package in Ubuntu: New Bug description: Hello, I have a new laptop. Very new model. acer 131t c1yf model 32 gb hard drive and 2 gb ram. Often the touchpad whimps out. Sometimes I can start it again by going into the mouse applet. Sometimes not. Sometimes if I plug in the mouse and unplug it, then it helps to get it back up. Sometimes it does not work and reboot is needed. Note. This is a touch pad model too. I have no idea on how to find the package at fault for this, so I picked the mouse applet. Bhikkhu Subhuti I hope this helps. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 21:31:27 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-01-25 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1538596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538596] Re: touchpad stops on acer 131t
I did the update finally and the problem still exists. I can still use my mouse. (sometimes that helps). I am actually in a frozen touchpad mode right now. It seems sure to happen. I am glad I have my mouse. I plugged and unplugged the mouse and it worked. (this bug happens without a mouse plugged in). You need to find a mouse, plug it in and unplug it a few times. I will try to find out the exact sequence to "cure" the problem, but I am doubtful I can duplicate it reliably. I suspect it is virtual memory though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1538596 Title: touchpad stops on acer 131t Status in unity-control-center package in Ubuntu: New Bug description: Hello, I have a new laptop. Very new model. acer 131t c1yf model 32 gb hard drive and 2 gb ram. Often the touchpad whimps out. Sometimes I can start it again by going into the mouse applet. Sometimes not. Sometimes if I plug in the mouse and unplug it, then it helps to get it back up. Sometimes it does not work and reboot is needed. Note. This is a touch pad model too. I have no idea on how to find the package at fault for this, so I picked the mouse applet. Bhikkhu Subhuti I hope this helps. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 21:31:27 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-01-25 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1538596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538596] [NEW] touchpad stops on acer 131t
Public bug reported: Hello, I have a new laptop. Very new model. acer 131t c1yf model 32 gb hard drive and 2 gb ram. Often the touchpad whimps out. Sometimes I can start it again by going into the mouse applet. Sometimes not. Sometimes if I plug in the mouse and unplug it, then it helps to get it back up. Sometimes it does not work and reboot is needed. Note. This is a touch pad model too. I have no idea on how to find the package at fault for this, so I picked the mouse applet. Bhikkhu Subhuti I hope this helps. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 21:31:27 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-01-25 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1538596 Title: touchpad stops on acer 131t Status in unity-control-center package in Ubuntu: New Bug description: Hello, I have a new laptop. Very new model. acer 131t c1yf model 32 gb hard drive and 2 gb ram. Often the touchpad whimps out. Sometimes I can start it again by going into the mouse applet. Sometimes not. Sometimes if I plug in the mouse and unplug it, then it helps to get it back up. Sometimes it does not work and reboot is needed. Note. This is a touch pad model too. I have no idea on how to find the package at fault for this, so I picked the mouse applet. Bhikkhu Subhuti I hope this helps. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 21:31:27 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-01-25 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1538596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
