[Bug 1267791] [NEW] Mongodb server don't start because of bad log folder owner
Public bug reported: If I install (or reinstall) the mongodb-server package everything is fine. At the end of the installation the server is properly started and clients can connect to it. At that time, the owner of the /var/log/mongodb folder is 'mongodb'. But as soon as the machine is rebooted the owner of this folder becomes 'root' and the server is unable to start. See the mongo.txt file for a bash script descripting the bug ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mongodb-server 1:2.4.6-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-44.67-generic 3.5.7.25 Uname: Linux 3.5.0-44-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 10 08:41:13 2014 MarkForUpload: True SourcePackage: mongodb UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mongodb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: mongo.txt https://bugs.launchpad.net/bugs/1267791/+attachment/3945274/+files/mongo.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
** Description changed: If I install (or reinstall) the mongodb-server package everything is fine. - At the end of the installation the server is properly started and + At the end of the installation the server is properly started and clients can connect to it. At that time, the owner of the /var/log/mongodb folder is 'mongodb'. But as soon as the machine is rebooted the owner of this folder becomes 'root' and the server is unable to start. See the mongo.txt file for a bash script descripting the bug + + The date of the Ubuntu installation is rather old now on this computer. + It means that I made a lot of dist upgrade and it could also be my fault + manualy modifing some system file. Am I the only in that case ? + + Please do not hesitate to ask me for more information or if I can be of + any help. + + Thanks, + + Nicolas + ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mongodb-server 1:2.4.6-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-44.67-generic 3.5.7.25 Uname: Linux 3.5.0-44-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 10 08:41:13 2014 MarkForUpload: True SourcePackage: mongodb UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
** Attachment added: /etc/init/mongodb.conf https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+attachment/3945376/+files/mongodb.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
** Attachment added: /etc/mongodb.conf https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+attachment/3945375/+files/mongodb.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
Hello Jörg, I tried the hotfix you suggested and it works. At the same time I tried a fresh install in a virtualbox and mongodb- server works out of the box. It seems I'm the only one to have this problem so it might come from something specific in my installation. Thanks for your help, Nicolas -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 128085] Re: Dell 1521 SB600 Azalia sound card not working in Feisty and Gutsy, working on Edgy (FIXABLE!)
Same Problem, but works fine with the alsa drivers which Eduardo recommended. -- Dell 1521 SB600 Azalia sound card not working in Feisty and Gutsy, working on Edgy (FIXABLE!) https://bugs.launchpad.net/bugs/128085 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248888] [NEW] Folder creation naming is canceled when name contains underscore with french bepo keyboard layout
Public bug reported: Step to reproduce : - select the french bepo keyboard in the list of layouts - open nautilus and create a folder - when it asks a name for the folder, try to give a name containing an underscore (AltGr+space on the bépo layout) - as soon as you press the AltGr key the focus is lost and the name of the folder stays «Untitled Folder» Remarks : - I am using a qwerty keyboard with the french bépo layout - There is no problem for entering underscore when I am renaming the previously created «Untitled Folder» ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 Date: Thu Nov 7 14:59:56 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1315x714+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'153' InstallationDate: Installed on 2013-06-10 (149 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248888] Re: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout
I think this key is not binded to anything but just to make sure I launched the keyboard tool. It seems binded to nothing but in english layout, pressing the key open the «command menu» (such as the left alt key does). But in bépo layout, it does nothing. So, in the tab «shortcut» I tryed to temporary set the AltGr key to some unused shortcut functionality : - When the qwerty layout is selected the key is recognize as a Alt R key; - When the bépo layout is selected the key is recognize as a Level 3 shift key. Please see the uploaded screenshot I don't know what is this kind of key Level 3 shift. Bépo layout is the equivalent of the dvorak layout (but applied to french). On a bépo keyboard layout, this AltGr key is useful for dealing with foreign language and input char like ñ ã ú ś ¿ ¡ ù ï © ß ... Remark, whenever I try to bind this Level 3 shift to a shortcut, the shortcut never works when the key is pressed. ** Attachment added: Two layout recognize the same physical key differently https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/124/+attachment/3902360/+files/ShortcutBindingRecognition.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248888] Re: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout
Referenced 712145 in gnome bugzilla . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248888] Re: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout
Additional remark : it only happens in list mode. In icon mode it works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Folder creation naming is canceled when name contains underscore with french bepo keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254376] Re: Brightness settings changes have no effect.
More information acpi_backlight=vendor Shortcut doesn't work at all (Fn+Left and Fn+Right). there is no OSD displayed anymore I can change the backlight from the system settings (doing so modifies the /sys/class/backlight/intel_backlight/brightness file) Writting from the console myself in /sys/class/backlight/intel_backlight/brightness changes the backlight level (8 dimm : the screen is almost off). video.use_bios_initial_backlight=0 : NO CHANGE compare to the initial report. I can control the backlight level from the console with the file /sys/class/backlight/intel_backlight/brightness file (8 dimm : the screen is almost off) but the software modifies the brigtness in the acpi folder instead. atkbd.softraw=0 : NO CHANGE compare to the initial report. I can control the backlight level from the console with the file /sys/class/backlight/intel_backlight/brightness file (8 dimm : the screen is almost off) but the software modifies the brigtness in the acpi folder instead. Show key result is Left 0xe0 0x4b 0xe0 0xcb Right 0xe0 0x4d 0xe0 0xcd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254376 Title: Brightness settings changes have no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1256196] [NEW] zeitgeist-fts uses a lot of memory (more than 200MB)
Public bug reported: Hi, I find that zeitgeist-fts process uses continuously a lot of memory between 10 and 20% of a 2GB laptop. See the attached screenshot. Is it a normal behavior ? I can provide the activity file if required. Nicolas ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: zeitgeist-core 0.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 Date: Fri Nov 29 09:37:44 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/zeitgeist/zeitgeist-fts InstallationDate: Installed on 2013-06-10 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: Screenshot from 2013-11-28 23:05:51.png https://bugs.launchpad.net/bugs/1256196/+attachment/3919485/+files/Screenshot%20from%202013-11-28%2023%3A05%3A51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256196 Title: zeitgeist-fts uses a lot of memory (more than 200MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1256196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258966] [NEW] Inconsistent behavior when quitting rhythmbox
Public bug reported: For a user there are three ways I know for quitting an application : - File-quit - Alt+F4 - Click on the cross of the window - Right click on the icon in the dash and select quit According to these 4 methods there are two cases to consider : either a music is played or not. While not playing : the application is always unloaded from the memory whichever the way used (that is good) While playing : only the quit option in the file menu really unload the application. The three others options rather hide the main windows (background play) so that : - it is impossible to remove the application from the memory without opening a new window; - it is difficult to predict what will be the behavior of closing the window or using the dash quit option. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 Date: Sun Dec 8 22:09:52 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2013-06-10 (181 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258966 Title: Inconsistent behavior when quitting rhythmbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1258966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875002] Re: choosing quit from unity launcher doesn't close rhythmbox if music is playing
There are also this unconsistency where right clicking on the dash icon and selecting the quit option behaves like clicking on the cross and not like the file-quit option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875002 Title: choosing quit from unity launcher doesn't close rhythmbox if music is playing To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/875002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267791] [NEW] Mongodb server don't start because of bad log folder owner
Public bug reported: If I install (or reinstall) the mongodb-server package everything is fine. At the end of the installation the server is properly started and clients can connect to it. At that time, the owner of the /var/log/mongodb folder is 'mongodb'. But as soon as the machine is rebooted the owner of this folder becomes 'root' and the server is unable to start. See the mongo.txt file for a bash script descripting the bug ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mongodb-server 1:2.4.6-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-44.67-generic 3.5.7.25 Uname: Linux 3.5.0-44-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 10 08:41:13 2014 MarkForUpload: True SourcePackage: mongodb UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mongodb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: mongo.txt https://bugs.launchpad.net/bugs/1267791/+attachment/3945274/+files/mongo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
** Description changed: If I install (or reinstall) the mongodb-server package everything is fine. - At the end of the installation the server is properly started and + At the end of the installation the server is properly started and clients can connect to it. At that time, the owner of the /var/log/mongodb folder is 'mongodb'. But as soon as the machine is rebooted the owner of this folder becomes 'root' and the server is unable to start. See the mongo.txt file for a bash script descripting the bug + + The date of the Ubuntu installation is rather old now on this computer. + It means that I made a lot of dist upgrade and it could also be my fault + manualy modifing some system file. Am I the only in that case ? + + Please do not hesitate to ask me for more information or if I can be of + any help. + + Thanks, + + Nicolas + ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mongodb-server 1:2.4.6-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-44.67-generic 3.5.7.25 Uname: Linux 3.5.0-44-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 10 08:41:13 2014 MarkForUpload: True SourcePackage: mongodb UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
** Attachment added: /etc/init/mongodb.conf https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+attachment/3945376/+files/mongodb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
** Attachment added: /etc/mongodb.conf https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+attachment/3945375/+files/mongodb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267791] Re: Mongodb server don't start because of bad log folder owner
Hello Jörg, I tried the hotfix you suggested and it works. At the same time I tried a fresh install in a virtualbox and mongodb- server works out of the box. It seems I'm the only one to have this problem so it might come from something specific in my installation. Thanks for your help, Nicolas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267791 Title: Mongodb server don't start because of bad log folder owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254376] [NEW] Brightness settings changes have no effect.
Public bug reported: On my laptop (acer aspire one V5-131) which uses Ubuntu 13.04, the change of the brightness settings have no effect on the brightness in the settings application. When I press the shortcut for changing the brightness (Fn+Left Fn+Right), the notification of the new brightness level is correctly displayed but again it has no effect on the brightness of the screen (and it neither update the level in the settings application). Please, see in the attached file (Brightness.txt) what I do for changing the brightness on my computer from the console. I don't know anything about the settings software stack but since it works from the console I don't think it is a driver problem but rather a software problem somewhere or maybe a missing symlink. Though the keyboard shortcut are not working properly, the problem could also be below gnome-control-center. Please contact me for any question or if I can be of any help for the correction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24.1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 Date: Sun Nov 24 07:39:09 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-06-10 (166 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1 gnome-control-center-unity 1.3daily13.06.19~13.04-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: Change the brigtness from the console. https://bugs.launchpad.net/bugs/1254376/+attachment/3915713/+files/Brightness.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254376 Title: Brightness settings changes have no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1254376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254376] Re: Brightness settings changes have no effect.
Here are the requested informations. As you will see there are two folders in /sys/class/backlight When I use the keyboards shortcuts to modify the brightness, the file /sys/class/backlight/acpi_video0/brightness is modified but it has no effect on the actual brightness. When I manually write the brightness into the file /sys/class/backlight/intel_backlight/brightness, the actual brightness is modified. Some software (like cairo dock manage to change the brightness). I guess they use the right folder. Nicolas ** Attachment added: Files requested on wiki.ubuntu.com https://bugs.launchpad.net/ubuntu/+bug/1254376/+attachment/3919207/+files/brightness_files.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254376 Title: Brightness settings changes have no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254376] Re: Brightness settings changes have no effect.
I confirm what Jankob said. With the same parameters on the grub command line, I have the same behavior on my 13.4 (kernel 3.8.0-34) : it works but no OSD notification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254376 Title: Brightness settings changes have no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277238] [NEW] The shortcut to the current playing song does't always work
Public bug reported: When I use a inteligent playlist (in my case the list of songs never played), I am unable to use the menu option (or ctrl+j) to go to the current playing song. While the music is playing (started from the inteligent playlist) if I go to the list of all the music I can't go to the current song with ctrl+J. It works with standard playlist (m3u). Please let me know if I can be of any help. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: banshee 2.6.1-2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Feb 6 20:50:42 2014 MarkForUpload: True SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: banshee (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277238 Title: The shortcut to the current playing song does't always work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1277238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368896] [NEW] hud-service 3G of memory and 50% of a core
Public bug reported: At the end of the day the hud-service process uses a lot of memory (3GB) and some CPU too (half a core at least). I don't know why. I am not using this functionality. Neither I know how to reproduce it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 14.04+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 12 19:33:15 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.hud.log: Hit DBusMenu safety valve closing menu at :1.131569 /com/canonical/menu/5C000B3 Hit DBusMenu safety valve opening menu at :1.131569 /com/canonical/menu/5C000B3 Hit DBusMenu safety valve closing menu at :1.131569 /com/canonical/menu/5C000B3 ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Summary changed: - hud-service 3G of memory and 50% of a cpu + hud-service 3G of memory and 50% of a core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368896 Title: hud-service 3G of memory and 50% of a core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1368896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327956] Re: Synaptic - unable to enter text in proxy authentication field
Hi, I've the same trouble on ubuntu 14.04 (almost fresh install). I managed to fill those fields using right click and then paste. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327956 Title: Synaptic - unable to enter text in proxy authentication field To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1327956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754274] Re: ubuntu-desktop is removed while applying security upgrade
apt history ** Attachment added: "apt_history.log" https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1754274/+attachment/5072734/+files/apt_history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754274 Title: ubuntu-desktop is removed while applying security upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1754274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754274] [NEW] ubuntu-desktop is removed while applying security upgrade
Public bug reported: Hello, I use to apply only security upgrade using the update-manager popup (therefore there are always remaining a bunch of minor upgrades that are not critical and I choose not to apply). This morning I applied the security updates. Unfortunately it ended up removing ubuntu-desktop:amd64 package leaving the ubuntu installation broken. Here is the extract of the apt log : ``` Start-Date: 2018-03-08 07:04:43 Commandline: aptdaemon role='role-commit-packages' sender=':1.1271' Upgrade: unity-schemas:amd64 (7.4.5+16.04.20171201.3, 7.4.5+16.04.20180221-0ubuntu1), compiz-plugins-default:amd64 (1:0.9.12.3+16.04.20171116-0ub untu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), libdecoration0:amd64 (1:0.9.12.3+16.04.20171116-0ubuntu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), compiz config-settings-manager:amd64 (1:0.9.12.2+16.04.20160823-0ubuntu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), python:amd64 (2.7.11-1, 2.7.12-1~16.04), libpq5:amd64 (9.5.11-0ubuntu0.16.04, 9.5.12-0ubuntu0.16.04), libpython-stdlib:amd64 (2.7.11-1, 2.7.12-1~16.04), unity-services:amd64 (7.4.5+16.04 .20171201.3, 7.4.5+16.04.20180221-0ubuntu1), compiz-gnome:amd64 (1:0.9.12.3+16.04.20171116-0ubuntu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), libcomp izconfig0:amd64 (1:0.9.12.3+16.04.20171116-0ubuntu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), code:amd64 (1.20.1-1518535978, 1.21.0-1520420608), pyth on-compizconfig:amd64 (1:0.9.12.2+16.04.20160823-0ubuntu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), compiz-core:amd64 (1:0.9.12.3+16.04.20171116-0ubu ntu1, 1:0.9.12.3+16.04.20180221-0ubuntu1), python-minimal:amd64 (2.7.11-1, 2.7.12-1~16.04) Remove: ubuntu-desktop:amd64 (1.361.1), unity:amd64 (7.4.5+16.04.20171201.3), session-shortcuts:amd64 (1.2ubuntu0.16.04.1), libunity-core-6.0-9:a md64 (7.4.5+16.04.20171201.3), unity-tweak-tool:amd64 (0.0.7ubuntu2) End-Date: 2018-03-08 07:05:20 ``` To repair it I had to manually install the package : ``` Start-Date: 2018-03-08 09:30:05 Commandline: apt install ubuntu-desktop Requested-By: thm (1000) Install: unity-schemas:amd64 (7.4.5+16.04.20180221-0ubuntu1, automatic), ubuntu-desktop:amd64 (1.361.1), unity:amd64 (7.4.5+16.04.20180221-0ubuntu1, automatic), deja-dup:amd64 (34.2-0ubuntu1.1, automatic), session-shortcuts:amd64 (1.2ubuntu0.16.04.1, automatic), libunity-core-6.0-9:amd64 (7.4.5+16.04.20180221-0ubuntu1, automatic), gnome-screensaver:amd64 (3.6.1-7ubuntu4, automatic) End-Date: 2018-03-08 09:30:17 ``` Maybe there is a package dependency problem here ? ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lsb_release.txt" https://bugs.launchpad.net/bugs/1754274/+attachment/5072733/+files/lsb_release.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754274 Title: ubuntu-desktop is removed while applying security upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1754274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
