[Bug 1829609] Re: files in sudoers.d no longer being read or honored
This bug appears to be related to KDEneon only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829609] Re: files in sudoers.d no longer being read or honored
This appears to be KDEneon only. Please close. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829609] [NEW] files in sudoers.d no longer being read or honored
Public bug reported: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add-repository stuart office = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: hostname (Ubuntu) Importance: Undecided Status: New ** Tags: sudo sudoers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584549] Re: sudoers not honoring hostnames
Now using 18.04 KDEneon and last month sometime an update broke this functionality even further. The FQDN and indeed no other format works any longer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Two immediately above comments reference EFI boot. This bug report and fix were regarding an original bug that appeared in non-EFI boot environment. It's possible your encountering a different bug or have an unclean EFI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814403 Title: Latest update causes 30 sec. menu delay timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Thanks for the quick fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814403 Title: Latest update causes 30 sec. menu delay timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Not using EFI here at all; BTRFS+GPT but no EFI. IMO forcing reference to EFI when it doesn't exist is poor programming for a universal tool like a boot manager. EFI should be included but gracefully enough not to cause problems. If the strong recommendation is to not set GRUB_RECORDFAIL_TIMEOUT to zero, why is it acceptable to delay boot for functionality that doesn't exist? Seems at a minimum the 00_header should be re-written to bypass the "lsefi" stanza if EFI is not in use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814403 Title: Latest update causes 30 sec. menu delay timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] [NEW] Latest update causes 30 sec. menu delay timeout
Public bug reported:
KDEneon LTS user edition 5.12, Release 18.04
grub-common 2.02-2ubuntu8.10 from Ubuntu updates
Since latest update near the end of Jan. 2019 (29th?), grub menu has 30
second delay every reboot as though recordfail is set. It did not do
this before the update.
After messing with grubenv and recordfails settings, I found this
paragraph in 00_header in 18.04 that is not in 16.04:
if lsefi; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi
Note "timeout=30" which is the same as the recordfail timeout. As a
test, I edited /boot/grub/grub.cfg and changed the 30 to 17 and sure
enough, that's the source of the timeout.
Here's the paragraph from 00_header:
if lsefi; then set timeout=${GRUB_RECORDFAIL_TIMEOUT:-30}
if [ x\$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi
One odd thing is the 00_header file is from Jan 9th but this bug has
just appeared so it must be related to grub-common not the the header
file.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814403
Title:
Latest update causes 30 sec. menu delay timeout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605230] Re: sub-directories initially only accessible by root
"*I had to change #!/bin.bash to #!/bin/bash to make it run" Silly typo, sorry. Worked here. I ran it again and inotifywait shows up in processes. Try it from the command line like this: while true; do inotifywait /shared/ >/dev/null 2>&1; ls /shared/* >/dev/null 2>&1; done If this works, then it's your script. If not - I have no clue. My folder structure is simple, /shared/ /Documents /Music /Pictures etc... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605230 Title: sub-directories initially only accessible by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1605230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1605230] Re: sub-directories initially only accessible by root
Sorry for not being more complete. What I did was create the script (I named it "keepalive" with the text I posted (all the stuff in-between the dashed lines) and save it in the /root folder. It must be executable ( sudo chmod +x /root/keepalive). Then call it from rc.local with /root/keepalive . Stuart Smith, from my Moto X On Sep 9, 2016 5:11 PM, "KeithP" <1605...@bugs.launchpad.net> wrote: > Thank you for the feedback! I’m fairly new to Linux in general, however; > I tried to implement the bash script by installing inotifywait and > adding the script to the /etc/rc.local file. It doesn’t seem to do > anything and when I do “ps – aux | grep inotifywait” the only thing > which is returned is my grep statement. I’ve noticed that when I edit > the rc.local file, it formats my share weirdly. I’m connecting to a DFS, > so my share name is “/domain.com/h5”, however; when I edit the rc.local > file in vi, it turns the “5” red, making me think it’s parsing “/h” as a > switch. I’ve since put quotation marks around the share name, but that > didn’t seem to make any difference. I was able to create an entry in the > crontab which seems to accomplish the same thing: > > */5 * * * * /bin/ls /mnt/username >nul > > Users used to be able to mount the drives themselves, as long as the > drive mapping was listed in the fstab, but I’ve noticed that trying to > mount requires sudo now, even if the share is listed in fstab: > > //domain.com/h5 /mnt/username cifs > user=WindowsUsersName,uid=username,gid=sudo,file_mode=0770,dir_mode=-0770 > 0 0 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1605230 > > Title: > sub-directories initially only accessible by root > > Status in nfs-utils package in Ubuntu: > Confirmed > > Bug description: > sub-directories initially only accessible by root > > Client: (K)Ubuntu 16.04 LTS - new install (not upgrade) fully up-to-date > Server: Ubuntu 14.04 LTS - fully up-to-date > Client Package: nfs-common 1:1.2.8-9ubuntu12 > > No access issues using Kubuntu 15.04 client in the past or currently. > Server configuration unchanged. > > Attempting to access all subfolders of NFS mount fails for user. > Primary folder is listable, subfolders are not, files in first level > folder are accessable. If a subfolder is accessed by root user, it > (and all nested subfolders and files) becomes accessible by users. > After an unknown amount of time, subfolders revert back to > inaccessible by user unless subfolder is kept "active" - like having > it open in Dolphin. Permissions appear correct. > > :~$ ll /shared > total 148 > drwxrwsr-x 1 nobody shared274 Jul 18 14:03 ./ > drwxr-xr-x 1 root root 262 Jul 16 12:41 ../ > drwxrwsr-x 1 nobody shared120 Jul 6 11:49 Audio/ > drwxrwsr-x 1 nobody shared 18 Jul 6 11:49 Backups/ > -rw--- 1 nobody shared 35 Jul 7 13:42 .directory > drwxrwsr-x 1 nobody shared612 Jul 8 09:12 Documents/ > > ~$ ll /shared/Audio/ > ls: cannot access '/shared/Audio/': Operation not permitted > > ~$ sudo ls /shared/Audio/ > [sudo] password: > Audio Books Comedy Holiday Ringtones > > :~$ ll /shared/Audio/ > total 0 > drwxrwsr-x 1 nobody shared 120 Jul 6 11:49 ./ > drwxrwsr-x 1 nobody shared 274 Jul 18 14:03 ../ > drwxrwsr-x 1 nobody shared 390 Jun 12 2011 Audio Books/ > drwxrwsr-x 1 nobody shared 4882 May 22 14:49 Comedy/ > drwxrwsr-x 1 nobody shared 166 Nov 22 2013 Holiday/ > drwxrwsr-x 1 nobody shared 1290 Jul 7 2015 Ringtones/ > > fstab same for both client versions (15.04, 16.04): > server:/ /shared nfs4 auto,bg,soft,users,rsize= > 65536,wsize=65536,noatime,x-systemd.automount 0 0 > server:/ /shared nfs4 auto,bg,soft,users,rsize= > 65536,wsize=65536,noatime,x-systemd.automount 0 0 > > export line from server: > /exports 192.168.1.0/24(rw,fsid=0,crossmnt,no_subtree_check, > async,secure,nohide,all_squash,anonuid=65534,anongid=560) > > client-side user groups: adm cdrom sudo dip backup plugdev users > lpadmin sambashare wireshark shared > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/ > 1605230/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605230 Title: sub-directories initially only accessible by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1605230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605230] Re: sub-directories initially only accessible by root
I recently moved the KDEneon 5.7.4 from 16.04 (clean install) and this issue is not present there, so it's potentially possible this is already fixed upstream from 16.04. I still have 16.04 and 15.04 available if any trouble shooting would be helpful... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605230 Title: sub-directories initially only accessible by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1605230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605230] Re: sub-directories initially only accessible by root
My workaround, an endless script using inotify running from rc.local: #!/bin.bash while true #run indefinitely do inotifywait /shared/ >/dev/null 2>&1 ls /shared >nul done This does a sudo listing of all the subdirectories of "/shared" anytime the root folder is accessed. Obviously, change /shared to match yours... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605230 Title: sub-directories initially only accessible by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1605230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584549] Re: sudoers not honoring hostnames
New info: Using the FQDN instead of the shortened hostname version works. As before, in 15.04 shortened hostname works in sudoers.d/ files but in 16.04 it does not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605230] [NEW] sub-directories initially only accessible by root
Public bug reported: sub-directories initially only accessible by root Client: (K)Ubuntu 16.04 LTS - new install (not upgrade) fully up-to-date Server: Ubuntu 14.04 LTS - fully up-to-date Client Package: nfs-common 1:1.2.8-9ubuntu12 No access issues using Kubuntu 15.04 client in the past or currently. Server configuration unchanged. Attempting to access all subfolders of NFS mount fails for user. Primary folder is listable, subfolders are not, files in first level folder are accessable. If a subfolder is accessed by root user, it (and all nested subfolders and files) becomes accessible by users. After an unknown amount of time, subfolders revert back to inaccessible by user unless subfolder is kept "active" - like having it open in Dolphin. Permissions appear correct. :~$ ll /shared total 148 drwxrwsr-x 1 nobody shared274 Jul 18 14:03 ./ drwxr-xr-x 1 root root 262 Jul 16 12:41 ../ drwxrwsr-x 1 nobody shared120 Jul 6 11:49 Audio/ drwxrwsr-x 1 nobody shared 18 Jul 6 11:49 Backups/ -rw--- 1 nobody shared 35 Jul 7 13:42 .directory drwxrwsr-x 1 nobody shared612 Jul 8 09:12 Documents/ ~$ ll /shared/Audio/ ls: cannot access '/shared/Audio/': Operation not permitted ~$ sudo ls /shared/Audio/ [sudo] password: Audio Books Comedy Holiday Ringtones :~$ ll /shared/Audio/ total 0 drwxrwsr-x 1 nobody shared 120 Jul 6 11:49 ./ drwxrwsr-x 1 nobody shared 274 Jul 18 14:03 ../ drwxrwsr-x 1 nobody shared 390 Jun 12 2011 Audio Books/ drwxrwsr-x 1 nobody shared 4882 May 22 14:49 Comedy/ drwxrwsr-x 1 nobody shared 166 Nov 22 2013 Holiday/ drwxrwsr-x 1 nobody shared 1290 Jul 7 2015 Ringtones/ fstab same for both client versions (15.04, 16.04): server:/ /shared nfs4 auto,bg,soft,users,rsize=65536,wsize=65536,noatime,x-systemd.automount 0 0 server:/ /shared nfs4 auto,bg,soft,users,rsize=65536,wsize=65536,noatime,x-systemd.automount 0 0 export line from server: /exports 192.168.1.0/24(rw,fsid=0,crossmnt,no_subtree_check,async,secure,nohide,all_squash,anonuid=65534,anongid=560) client-side user groups: adm cdrom sudo dip backup plugdev users lpadmin sambashare wireshark shared ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605230 Title: sub-directories initially only accessible by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1605230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584549] [NEW] sudoers not honoring hostnames
Public bug reported: New Kubuntu 16.04 install, adding features from previous 15.04 install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04 but it does not work as expected. File contents: myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get, /usr/bin/add-apt-repository results in 15.04 in user "myusername" being able to run apt, apt-get, and add-apt-repository from the CLI using sudo without a password prompt. However, same exact syntax in 16.04 results in password prompt. In the 16.04 install, changing "myhostname" to "ALL" resumes the no password behavior. Both installs have exact same /etc/hosts files, running on bare metal on the same system, and the "hostname" command results in the same reply with the correct hostname. I have compared the subject files several times and there are no differences. No errors editing any of the files using visudo. Permissions and syntax same on both systems. This leads me to conclude sudoers is not honoring the hostname in the sudoers file(s). ** Affects: hostname (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529450] Re: [master] AttributeError: 'PageKde' object has no attribute 'get_secureboot_key'
I've been trying Andrew's solution over the last few days. Failed until today's daily build 01-28-2016, now appears to be working. Grab this ISO if you want to try it out. Thanks Andrew. The lines in question are 344,347,348 so I used sed instead of pico. This one-liner worked here for me: sudo sed -i '344 s/^/#/; 347 s/^/#/; 348 s/^/#/' /usr/lib/ubiquity/plugins/ubi-prepare.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529450 Title: [master] AttributeError: 'PageKde' object has no attribute 'get_secureboot_key' To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1529450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
For what it's worth, it seems it might be HOW the script is being called. Testing the apt-auto-removal script here (Kubuntu 15.04) with kernels 3.19.0-29-generic, 3.19.0-30-generic, and 3.19.0-31-generic installed and after a reboot to load -31: 1) Noticed the call to autoremove 3.19.0-30-generic. 2) Read /etc/apt/apt.conf.d/01autoremovekernels and saw -29 and -31 listed as "NeverAutoRemove" 3) Manually removed 3.19.0-29-generic. 4) Ran "sudo /etc/kernel/postinst.d/apt-auto-removal" 5) Re-read /etc/apt/apt.conf.d/01autoremovekernels and saw only -31 listed as "NeverAutoRemove" 6) Ran "sudo /etc/kernel/postinst.d/apt-auto-removal 3.19.0-31-generic" 7) Re-read /etc/apt/apt.conf.d/01autoremovekernels and saw -30 and -31 listed as "NeverAutoRemove" So it worked when called properly in that case. I thought it possible that part of the problem is it's being called with the wrong kernel version. I re-installed -25 and -21 along with -30 and -31. This resulted in -25 and -31 in the never remove list. But again: When apt-auto-removal is re-run with -31, the never remove list changes to -30 and -31. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440608 Title: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314443] [NEW] mlocate updatedb not searching home on btrfs
Public bug reported: Kubuntu 14.04, new install mlocate Installed: 0.26-1ubuntu1 Running updatedb does not include /home subdirectories in the file scan. Editing /etc/updatedb.conf and remarking out PRUNE_BIND_MOUNTS=yes results in a successful /home file scan. This behavior is a change from 13.10, where updatedb and updatedb.conf worked as expected. I suspect this may be due to /home being a mounted btrfs subvolume. However, as I stated, this worked fine using 13.10. ** Affects: mlocate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314443 Title: mlocate updatedb not searching home on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1314443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504440] Re: sd card safely remove drive kills reader device
Wow, this bug has persisted from 9.10 to 13.04. Is this ever going to be addressed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/504440 Title: sd card safely remove drive kills reader device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/504440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1180400] Re: New User creation results in nearly bare panel
Yeah - that was it. I obviously didn't find that bug. I shoulda looked harder :( On Thu, May 16, 2013 at 12:10 PM, Steve Riley st...@rileyz.net wrote: Oshun... looks like this is being tracked in bug 1174689, and might be specific to multi-monitor setups. How many monitors do you have? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1180400 Title: New User creation results in nearly bare panel Status in “kubuntu-meta” package in Ubuntu: New Bug description: Behavior: Upon creation of a new user, logging into that new users account results in a desktop with a Folder View widget and a panel. Panel only contains the Activity Manager widget and nothing else. Expected Behavior: Panel should contain System Tray, Task Switcher, Lancelot, Digital Clock, Folder View, and Show Desktop. Reproducible: Always. Work Around: Manually add the above widgets On up-to-date Kubuntu 13.04 via upgrade from new 12.10 install (due to failure of Ubiquity in 13.04 to access hard drive partitions). 12.10 install was not used prior to upgrade except to fully update before upgrading. Hardware: Asus Maximus Formula SE, Q6600, XFX Alpha Dog nVidia GT8800 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: kubuntu-desktop 1.276 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed May 15 06:46:48 2013 MarkForUpload: True SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to raring on 2013-03-23 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1180400/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180400 Title: New User creation results in nearly bare panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1180400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180400] Re: New User creation results in nearly bare panel
Mark as duplicate of [url=https://bugs.launchpad.net/bugs/1174689]bug 1174689[/url] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180400 Title: New User creation results in nearly bare panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1180400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180400] [NEW] New User creation results in nearly bare panel
Public bug reported: Behavior: Upon creation of a new user, logging into that new users account results in a desktop with a Folder View widget and a panel. Panel only contains the Activity Manager widget and nothing else. Expected Behavior: Panel should contain System Tray, Task Switcher, Lancelot, Digital Clock, Folder View, and Show Desktop. Reproducible: Always. Work Around: Manually add the above widgets On up-to-date Kubuntu 13.04 via upgrade from new 12.10 install (due to failure of Ubiquity in 13.04 to access hard drive partitions). 12.10 install was not used prior to upgrade except to fully update before upgrading. Hardware: Asus Maximus Formula SE, Q6600, XFX Alpha Dog nVidia GT8800 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: kubuntu-desktop 1.276 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed May 15 06:46:48 2013 MarkForUpload: True SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to raring on 2013-03-23 (52 days ago) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1180400 Title: New User creation results in nearly bare panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1180400/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1131852] Re: WISH: Allow more control of BTRFS install
I fail to see how the option to allow the user to select a subvolume name other than @ for root and @home for /home would apply in the above linked instance. Unless I am reading that information incorrectly, as long as the corresponding subvolumes described in the mount options for / and /home reside immediately below the default mounting subvolume (level 5) there should be no difference. I have no problems booting to any BTRFS subvolume name I use. I'm only asking to have control over the NAME of the installation subvolumes, not to change the level in the btrfs tree. It seems this is a Ubiquity induced problem, not a btrfs limitation. Thanks anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1131852 Title: WISH: Allow more control of BTRFS install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1131852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1131852] [NEW] WISH: Allow more control of BTRFS install
Public bug reported: First let me say a big Thank You to implementing BTRFS as an install option and the genius move to have it automatically create a @home subvolume at install. Here's my Wishlist request to enhance the installer for advanced BTRS users: CHANGE: When BTRFS is selected, allow the user to designate subvolume assignment. Default to @ for root and @home for home, but allow editing of these subvolume names for advanced users REASONING: The best use of BTRFS in many cases is as a whole drive filesystem - no partitions at all. This introduces many benefits, one of which is using subvolumes to allow a single BTRFS filesystem to hold several different distro installs. CURRENTLY: I have a five drive system divided into three BTRFS filesystems. My SSD has three distros on it which reside in unique subvolumes. Steps to do this: I install a new distro to the BTRFS filesystem. Once complete, edit the associated boot/grub/grub.cfg and etc/fstab files renaming the @ and @home subvolumes to new unique names. Boot to a different distro or liveUSB and rename the subvolumes to the new names. Reboot into the new install and run update-grub. Done. CONCEPT: At install time, I select Manual Partitioning. When I select a BTRFS partition, an additional option to Create Subvolumes appears. The new option has a list allowing mount points to be assigned to subvolume names and has / set @ and /home set as @home by default. I change / to @kubuntu1210 and /home to @home_kubuntu1210. An additional option to add more subvolume mount assignments is available for those who want more subvolume assignments. RESULTS: No change to the basic install for BTRFS users but those of us who want to multi-boot and use large BTRFS filesystems to do that don't have to jump through so many hoops. Thanks for listening. If anyone want to contact me directly for clarification or wants to argue about the above, I'm on Kubuntu and Ubuntu forums as oshunluvr ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1131852 Title: WISH: Allow more control of BTRFS install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1131852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871307] Re: UDisks.Device.DriveDetach() permanently powers down card *reader*
Not to complain (much) but this bug has been around in various forms since at least 2009 and still is. I'm one of those with an internally mounted USB bus sd card reader that powers down if you use Safely Remove. Un-mount works well, but I am left to using the command line to do it. Is anyone interested in getting this fixed? I've literally read dozens if not a hundred different reports of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871307 Title: UDisks.Device.DriveDetach() permanently powers down card *reader* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/871307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080701] Re: After 'Preparing to install Ubuntu' screen, raring installation hangs
Re. the partition configurations causing this: My system has five drives and NO extended partitions on any of them. Drive 1: part. 1 swap, part. 2 BTRFS Drives 2-5: All BTRFS full drive filesystems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1080701 Title: After 'Preparing to install Ubuntu' screen, raring installation hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1080701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080701] Re: After 'Preparing to install Ubuntu' screen, raring installation hangs
Bug still there. Post #41 did not work for me. Last snipet from installer log: Jan 29 01:09:39 debconf (filter): -- GET partman-auto/disk debconf (developer): -- GET partman-auto/disk debconf (developer): -- 1 EOF -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1080701 Title: After 'Preparing to install Ubuntu' screen, raring installation hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1080701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081245] Re: Ubuntu 13.04 Live-CD Installer hangs
*** This bug is a duplicate of bug 1080701 *** https://bugs.launchpad.net/bugs/1080701 This bug still present as of daily build 21-Jan. I have no extended partitions on any drive as all my drives are btrfs single filesystems except sda which has a single swap partition. Using nodmraid at boot did not bypass this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081245 Title: Ubuntu 13.04 Live-CD Installer hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1081245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575428] Re: policykit authorization in KDE Lucid systemsettings is absent
So the KDE Team says it's Kubuntu Teams' fault and Kubuntu Team says it's KDE's??? -- policykit authorization in KDE Lucid systemsettings is absent https://bugs.launchpad.net/bugs/575428 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to polkit-kde-1 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 275451] Re: nfs mounts specified in fstab is not mounted on boot.
Upgrading to 9.10 did NOT solve this for me. -- nfs mounts specified in fstab is not mounted on boot. https://bugs.launchpad.net/bugs/275451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275451] Re: nfs mounts specified in fstab is not mounted on boot.
I noticed mt install no longer has a mountnfs.sh in /etc/init.d or any other location. -- nfs mounts specified in fstab is not mounted on boot. https://bugs.launchpad.net/bugs/275451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275451] Re: nfs mounts specified in fstab is not mounted on boot.
It seems my issue was caused by network manager. Issuing the command sudo update-rc.d -f NetworkManager remove fixed it for me. -- nfs mounts specified in fstab is not mounted on boot. https://bugs.launchpad.net/bugs/275451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454134] Re: openoffice calc is crasing on moving sheet with drag and drop
I have same issue - openoffice.org-kde removal solves it. System info: Kubuntu 9.10 Karmic Koala 2.6.31-17-generic #54-Ubuntu SMP x86_64 GNU/Linux openoffice.org-core 1:3.1.1-5ubuntu1 OpenOffice.org 3.1.1 OOO310m19 (Build:9420) -- openoffice calc is crasing on moving sheet with drag and drop https://bugs.launchpad.net/bugs/454134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
I am now seeing an additional udev/hal problem when using VirtualBox. I believe this is related to the above issue. VitrualBox Error Message: Could not access USB on the host system, because neither the USB file system (usbfs) nor the DBus and hal services are currently available. If you wish to use host USB devices inside guest systems, you must correct this and restart VirtualBox. The USB Proxy Service could not be started, because neither the USB file system (usbfs) nor the hardware information service (hal) is available. -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
I am still experiencing this bug. Requested files below ** Attachment added: lshal.txt http://launchpadlibrarian.net/34499889/lshal.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: ck-list-sessions.txt http://launchpadlibrarian.net/34499946/ck-list-sessions.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: id_haldaemon.txt http://launchpadlibrarian.net/34500043/id_haldaemon.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: devices.txt http://launchpadlibrarian.net/34500017/devices.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: dmesg.txt http://launchpadlibrarian.net/34500028/dmesg.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: udevlog.txt http://launchpadlibrarian.net/34500070/udevlog.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: uname.txt http://launchpadlibrarian.net/34500072/uname.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452768] Re: USB flash drive does not mount automatically
** Attachment added: hallog.txt http://launchpadlibrarian.net/34500172/hallog.txt -- USB flash drive does not mount automatically https://bugs.launchpad.net/bugs/452768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275451] Re: nfs mounts specified in fstab is not mounted on boot.
I'm having this problem 9.04 jaunty kubuntu install. Bonded interfaces and static IP caused problems with network manager. I removed network manager and then noticed the NFS mounts not auto-mounting a boot. Not sure when the behavior actually started. I'm planning a parallel install on this machine so I will report more info when I have it. -- nfs mounts specified in fstab is not mounted on boot. https://bugs.launchpad.net/bugs/275451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
