[Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
Just upgraded to 20.10 and the bundled LibreOffice version (7.0.2.2) and
have the same issue.
I can confirm mvaldez's fix for adding access for the GPG agent worked
for me. However, I didn't change the "@{HOME}/.gnupg/*" directive to rw
(I don't really want LibreOffice having write access to my gpg stuff!
Seems to work fine for me for choosing my key from tools->options or
File->Digital Signatures then "Sign Document". Clicking "Start
Certificate Manager" launches seahorse as expected.
Wouldn't it be better to somehow hook this value to GPG_AGENT_INFO or
XDG_RUNTIME_DIR though?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886092
Title:
libreoffice doesn't list gpg private key for a digital signature due
to apparmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850980] Re: mysql-server causes logrotate.service to fail at boot
Thanks for the feedback, Andreas. If the logrotate service is ONLY supposed to be triggered via the timer, then that could be a separate bug as it is definitely running on every boot on my 19.10 install. I took the exit status of the ping command from the man page for mysqladmin and also performed some basic testing. As far as I can tell, it works as expected even during MySQL start-up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850980 Title: mysql-server causes logrotate.service to fail at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850980] Re: mysql-server causes logrotate.service to fail at boot
I've crated a merge request to improve the postrotate script to more accurately detect the difference between mysqld not running and a problem with the configured debian-sys-maint config:- https://salsa.debian.org/mariadb-team/mysql/merge_requests/29 This will prevent the logrotate service from reporting a startup failure during boot if mysqld is not read to accept connections at the time the postrotate script is run. However, it will not prevent the potential situation where log files have been rotated but "mysqladmin flush-logs" is not called (because the postrotate script thinks mysqld is not running). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850980 Title: mysql-server causes logrotate.service to fail at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850980] [NEW] mysql-server causes logrotate.service to fail at boot
Public bug reported: Description --- During boot, systemd starts logrotate service and mysql server at the same time. However, at "random" the logrotate service will report a failure to run with an error message pointing to the mysql logrotate configuration. After some digging I found this to be a race condition within the postrotate script within the /etc/logrotate.d/mysql-server configuration file. The postrotate script first tries to check connectivity to the mysql server using "mysqladmin ping", if that fails it then checks for the existence of a mysqld process using "killall -q -s0 -umysql mysqld". If such a process exists, it assumes that this is a miss-configuration with the debian-sys-maint user and exits with en error (exit 1). This is not the case though. MySQL is just in the process of starting up, so the mysqld process exists but the server is not yet ready to accept connections. ``` -- Reboot -- Oct 31 09:27:25 ryzen1910 systemd[1]: Starting Rotate log files... Oct 31 09:27:25 ryzen1910 systemd[1]: logrotate.service: Succeeded. Oct 31 09:27:25 ryzen1910 systemd[1]: Started Rotate log files. -- Reboot -- Nov 01 08:11:35 ryzen1910 systemd[1]: Starting Rotate log files... Nov 01 08:11:35 ryzen1910 logrotate[1528]: error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/*log ' Nov 01 08:11:35 ryzen1910 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Nov 01 08:11:35 ryzen1910 systemd[1]: logrotate.service: Failed with result 'exit-code'. Nov 01 08:11:35 ryzen1910 systemd[1]: Failed to start Rotate log files. ``` Impact -- I am not familiar enough with logrotate to know if this has more serious consequences than simply not rotating the logs until the next time logrotate is triggered via cron. As the service is defined as a "oneshot" type, my assumption is that this is only triggered on boot to overcome the fact that the system could have been powered off at the time logrotate was scheduled to run via cron. Because it is the postrotate script that fails, mysqld could be in the state where it's log files have been rotated but "mysqladmin flush-logs" has not been triggered. I guess there could be other consequences of mysqld having it's log file rotated while it is in the process of starting up. System Details -- Release: Ubuntu 19.10 mysql-server Version: 8.0.17-0ubuntu2 Expected Behaviour -- MySQL's log files will be rotated on boot if needed and mysqld will be requested to flush it's logs. Actual Behaviour MySQL's log files might actually be rotated, but the flush logs command will not be executed and the logrotate.service reports an error in starting up. ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: Description --- During boot, systemd starts logrotate service and mysql server at the same time. However, at "random" the logrotate service will report a failure to run with an error message pointing to the mysql logrotate configuration. After some digging I found this to be a race condition within the postrotate script within the /etc/logrotate.d/mysql-server configuration file. The postrotate script first tries to check connectivity to the mysql server using "mysqladmin ping", if that fails it then checks for the existence of a mysqld process using "killall -q -s0 -umysql mysqld". If such a process exists, it assumes that this is a miss-configuration with the debian-sys-maint user and exits with en error (exit 1). This is not the case though. MySQL is just in the process of starting up, so the mysqld process exists but the server is not yet ready to accept connections. ``` -- Reboot -- Oct 31 09:27:25 ryzen1910 systemd[1]: Starting Rotate log files... Oct 31 09:27:25 ryzen1910 systemd[1]: logrotate.service: Succeeded. Oct 31 09:27:25 ryzen1910 systemd[1]: Started Rotate log files. -- Reboot -- Nov 01 08:11:35 ryzen1910 systemd[1]: Starting Rotate log files... Nov 01 08:11:35 ryzen1910 logrotate[1528]: error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/*log ' Nov 01 08:11:35 ryzen1910 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Nov 01 08:11:35 ryzen1910 systemd[1]: logrotate.service: Failed with result 'exit-code'. Nov 01 08:11:35 ryzen1910 systemd[1]: Failed to start Rotate log files. ``` - Impact -- I am not familiar enough with logrotate to know if this has more serious consequences than simply not rotating the logs until the next time logrotate is triggered via cron. As the service is defined as a "oneshot" type, my assumption is that this is only triggered on boot to overcome the fact that the system could have been powered off at the time logrotate was scheduled to run via cron. Because it is the postrotate script that
[Bug 1558471] Re: logrotate config mysql-server fails with error "error: skipping "/var/log/mysql.log"
Just hit this exact same issue with MySQL 8 and 19.10. Patch also fixes the problem on these versions too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558471 Title: logrotate config mysql-server fails with error "error: skipping "/var/log/mysql.log" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1558471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753837] Re: GRUB_GFXMODE no longer supports high resolution since upgrading to 2.02~beta3-4ubuntu7.2
*** This bug is a duplicate of bug 1752767 *** https://bugs.launchpad.net/bugs/1752767 The fix for removing the "--append" flag in https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1752767 also fixes this. I removed the flag from /etc/grub.d/00_header and updated and on the next reboot, grub was happily running at 2560x1440 (and with a background image). ** This bug has been marked a duplicate of bug 1752767 grub2 regression, simultaneous console and video graphical glitches with new patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753837 Title: GRUB_GFXMODE no longer supports high resolution since upgrading to 2.02~beta3-4ubuntu7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1753837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753837] [NEW] GRUB_GFXMODE no longer supports high resolution since upgrading to 2.02~beta3-4ubuntu7.2
Public bug reported: For months, my EFI grub has been happy to accept GRUB_GFXMODE=2560x1440 (my monitor native resolution). However, since the recent update to 2.02~beta3-4ubuntu7.2, all I get is a < 1s flash of the high resolution version (with background image) then it falls back to white on grey. If I comment out the GRUB_GFXMODE and GRUB_BACKGROUND lines, and "update-grub", I get a low resolution version with the background image still in place, and some flickering text artefacts. With the config as show below with GRUB_GFXMODE=1024x768 and GRUB_BACKGROUND="..." I get a working grub, although at a lower resolution which looks a bit crappy. Although this might seem a fairly trivial bug in terms of actual impact, I do have a dual boot machine and I hop between Linux and Windows a few times a day, and I like it when grub looks nice and crisp. System is an AMD Ryzen 1800X, Hero Vi Motherboard and Nvidia 1080Ti GFX card. ➜ ~ apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.02~beta3-4ubuntu7.2 Candidate: 2.02~beta3-4ubuntu7.2 Version table: *** 2.02~beta3-4ubuntu7.2 500 500 http://gb.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.02~beta3-4ubuntu7 500 500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful ➜ ~ cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=saved GRUB_SAVEDEFAULT=true #GRUB_HIDDEN_TIMEOUT=0 #GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_TIMEOUT_STYLE=menu GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE=1024x768 GRUB_BACKGROUND="/boot/grub/grub_background.png" # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" ** 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/1753837 Title: GRUB_GFXMODE no longer supports high resolution since upgrading to 2.02~beta3-4ubuntu7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1753837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713020] Re: Ubuntu Dock extension cannot be disabled in the Ubuntu session
Sorry. By bad on the login description! I was confusing "Ubuntu" and "Unity" - damn this transition phase :-( If I choose "Ubuntu on X.org" I cannot disable the dock, but if I choose "GNOME on X.org" I can. However, I still think this bug stands. Ether stop the extension from showing in Tweak Tool, or allow us to disable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713020 Title: Ubuntu Dock extension cannot be disabled in the Ubuntu session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1713020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713020] Re: Ubuntu Dock extension cannot be disabled in the Ubuntu session
I'm really confused now. I've upgraded to 17.10. On my login screen I choose "GNOME on X.org" and NOT "Ubuntu". I too see the option in tweak tool to disable ubuntu dock, but toggling the switch has no effect. So the answer "Install gnome-session" for a vanilla gnome doesn't seem to actually work. (At least not for some upgrade paths). So, like Joseph Jasson wrote, one way or another there is a bug. Either in the tweak tool or in the extension itself. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713020 Title: Ubuntu Dock extension cannot be disabled in the Ubuntu session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1713020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722468] [NEW] gnome-shell crashed with SIGABRT in g_assertion_message()
Private bug reported: Prior to the crash, there is a delay of about 30 seconds where the entire desktop is frozen and no mouse interactions register and no windows are updated. After which, the gnome shell restarts and everything is exactly as it was before the crash, fully functional again. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:14:47 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_handle_ungrabbed_event () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-08-31 (39 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722468 Title: gnome-shell crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Example audio created with "arecord -f cd". >From participants on various chat programs, the distortion is worse than it sounds here, so I'm trying to figure out if I can get a second test recorded via pulseaudio and not ALSA directly (I understand that is what arecord does). ** Attachment added: "created_with_arecord_dash_f_cd.wav" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+attachment/4948650/+files/created_with_arecord_dash_f_cd.wav -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716654] [NEW] [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Public bug reported: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Here is some updated system details for my latest hardy based server which still exhibits this behaviour:- $ uname -a Linux uc01 2.6.24-23-xen #1 SMP Thu Nov 27 20:14:09 UTC 2008 x86_64 GNU/Linux $ mysql --version mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (x86_64) using readline 5.2 $ dpkg -l |grep mysql-server ii mysql-server5.0.51a-3ubuntu5.4MySQL database server (meta package dependin ii mysql-server-5.05.0.51a-3ubuntu5.4MySQL database server binaries -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Wow! This bug is still alive and kicking - I had all but forgotten about it. Since it's just over a year since I first reported it, lets see if we can come up with a fix/patch. I know almost nothing about how the apt packages work and even less about configuring syslog but I suspect for the people the do know each of these subjects, the following questions/tasks will probably have pretty short answers. 1.) The mysql-server package needs to be reconfigured to put mysql.err and mysql.log into the empty /var/log/mysql directory. Maybe the actual log files should just be called error and info. 2.) logrotate needs to be updated to find the log files in the new locations. 3.) Syslog needs a configuration file/parameter to log mysql info to /var/log/mysql/mysql.err and /var/log/mysql/mysql.log 4.) Perhaps the default my.cnf file needs updating to suggest that users make use of the /var/log/mysql/ location for any other mysql related logging requirements. -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Here is some updated system details for my latest hardy based server which still exhibits this behaviour:- $ uname -a Linux uc01 2.6.24-23-xen #1 SMP Thu Nov 27 20:14:09 UTC 2008 x86_64 GNU/Linux $ mysql --version mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (x86_64) using readline 5.2 $ dpkg -l |grep mysql-server ii mysql-server5.0.51a-3ubuntu5.4MySQL database server (meta package dependin ii mysql-server-5.05.0.51a-3ubuntu5.4MySQL database server binaries -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 197522] Re: desktop-7.10-amd64 Hangs on CD boot
while hanged press ctrl alt f2 to display the root login ( your machine name login actually) login with your administrator account sudo vi /etc/default/bluetooth switch the variable BLUETOOTH_ENABLED from 1 to 0 (zero) save the file reboot the only way for me to solve the problem I hope this helps -- desktop-7.10-amd64 Hangs on CD boot https://bugs.launchpad.net/bugs/197522 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 72097] Re: init.d script only seems to be seeing first auth_mech
Wow, I filed that bug almost two years ago this week! I have actually discontinued hosting my own email server and switched all my clients over to google apps, but I'll see if I have some time this weekend to recreate with 8.04 or 8.10 using my old setup notes. -- init.d script only seems to be seeing first auth_mech https://bugs.launchpad.net/bugs/72097 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- 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 72097] Re: init.d script only seems to be seeing first auth_mech
Wow, I filed that bug almost two years ago this week! I have actually discontinued hosting my own email server and switched all my clients over to google apps, but I'll see if I have some time this weekend to recreate with 8.04 or 8.10 using my old setup notes. -- init.d script only seems to be seeing first auth_mech https://bugs.launchpad.net/bugs/72097 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Sorry for digging up an old bug, but perhaps /var/log/mysql.err / .log need to be removed then? -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Sorry for digging up an old bug, but perhaps /var/log/mysql.err / .log need to be removed then? -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Sorry for digging up an old bug, but perhaps /var/log/mysql.err / .log need to be removed then? -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
Sorry for digging up an old bug, but perhaps /var/log/mysql.err / .log need to be removed then? -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
I thought the point of syslog was to log everything and then also have other things logged to different files by adding directives to /etc/syslog.conf. The logs for postfix seem to be going into both /var/log/syslog and /var/log/mail.log Are there only special services that can be handled this way? or are we just missing some syslog.conf directives? -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 155466] Re: MySQL Query Browser ignores port number
I think this is actually a feature of the client library. If you specify localhost it uses the local socket (or named pipe on windows) to connect. To force it to use TCP/IP as you have correctly spotted, use the loopback interface (127.0.0.1) It has been this way for quite some time as I was aware of this behaviour very early on in my PHP development days which must have been version 3 or 4. -- MySQL Query Browser ignores port number https://bugs.launchpad.net/bugs/155466 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 185139] Default installation does not log to /var/log/mysql.err or mysql.log
Public bug reported: Binary package hint: mysql-server-5.0 Although /var/log/mysql.err and mysql.log files are created, they remain empty. Messages are logged to /var/log/syslog $uname -a Linux mysql-01 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT 2007 x86_64 GNU/Linux $ mysql --version mysql Ver 14.12 Distrib 5.0.45, for pc-linux-gnu (x86_64) using readline 5.2 My first bug report, hope its OK! ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 105457] Re: mysqd_safe high cpu usage
Oops, forgot some version info... MySQL Version = 5.0.45-Debian_1ubuntu3.1-log uname -a = Linux mysql-01 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT 2007 x86_64 GNU/Linux -- mysqd_safe high cpu usage https://bugs.launchpad.net/bugs/105457 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 105457] Re: mysqd_safe high cpu usage
I have also seen this problem today on MySQL. My /var/log/mysql.err and .log files are also empty, I suspect this is another bug where the installation file is not configuring syslogd properly. However, below are some lines from /var/log/syslog. After I noticed that mysqld_safe was at 100% cpu, I issued a mysqladmin shutdown. (Note, up until that point the server and database were still running fine) I suspect the first mysqld_safe[15155]: ended message is from the shutdown command and the second is the one I manually killed of via top. Jan 22 14:27:24 mysql-01 -- MARK -- Jan 22 14:30:45 mysql-01 mysqld[13897]: 080122 14:30:45 [Note] /usr/sbin/mysqld: Normal shutdown Jan 22 14:30:45 mysql-01 mysqld[13897]: Jan 22 14:30:47 mysql-01 mysqld[13897]: 080122 14:30:47 InnoDB: Starting shutdown... Jan 22 14:30:52 mysql-01 mysqld[13897]: 080122 14:30:52 InnoDB: Shutdown completed; log sequence number 0 71517936 Jan 22 14:30:52 mysql-01 mysqld[13897]: 080122 14:30:52 [Note] /usr/sbin/mysqld: Shutdown complete Jan 22 14:30:52 mysql-01 mysqld[13897]: Jan 22 14:30:52 mysql-01 mysqld_safe[15155]: ended Jan 22 14:43:42 mysql-01 mysqld_safe[15180]: ended Jan 22 14:44:04 mysql-01 mysqld_safe[15279]: started Jan 22 14:44:08 mysql-01 mysqld[15282]: 080122 14:44:08 InnoDB: Started; log sequence number 0 71517936 Jan 22 14:44:08 mysql-01 mysqld[15282]: 080122 14:44:08 [Note] /usr/sbin/mysqld: ready for connections. Jan 22 14:44:08 mysql-01 mysqld[15282]: Version: '5.0.45-Debian_1ubuntu3.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution Jan 22 14:44:08 mysql-01 /etc/mysql/debian-start[15344]: Upgrading MySQL tables if necessary. Jan 22 14:44:09 mysql-01 /etc/mysql/debian-start[15348]: Looking for 'mysql' in: /usr/bin/mysql Jan 22 14:44:09 mysql-01 /etc/mysql/debian-start[15348]: Looking for 'mysqlcheck' in: /usr/bin/mysqlcheck Jan 22 14:44:09 mysql-01 /etc/mysql/debian-start[15348]: This installation of MySQL is already upgraded to 5.0.45, use --force if you still need to run mysql_upgrade Jan 22 14:44:09 mysql-01 /etc/mysql/debian-start[15357]: Checking for insecure root accounts. Jan 22 14:44:09 mysql-01 /etc/mysql/debian-start[15361]: Checking for crashed MySQL tables. -- mysqd_safe high cpu usage https://bugs.launchpad.net/bugs/105457 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 185139] Re: Default installation does not log to /var/log/mysql.err or mysql.log
[EMAIL PROTECTED]:~$ dpkg -l |grep mysql-server ii mysql-server 5.0.45-1ubuntu3.1 MySQL database server (meta package dependin ii mysql-server-5.0 5.0.45-1ubuntu3.1 MySQL database server binaries -- Default installation does not log to /var/log/mysql.err or mysql.log https://bugs.launchpad.net/bugs/185139 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 72097] init.d script only seems to be seeing first auth_mech
Public bug reported:
Binary package hint: libsasl2
If I set the MECHANISMS in /etc/defaults/saslauthd to pam rimap, when
saslauthd is started by the init.d script, it loads only pam. However,
If I just have 1 auth_mech, then that one seems to work OK.
I redirected the output of saslauthd to /var/log/sasl.log and added the
-V option. Snippet 1 below shows a single auth_mech working. Snippet 2
shows the second one (rimap) seems to get forgotten.
I hope I haven't made a silly mistake and wasted any-ones time.
Paul
(aka. Gargoyle)
--- 8 Snippit 1 8 ---
-- /etc/defaults/saslauthd --
# This needs to be uncommented before saslauthd will be run automatically
# START=yes
# You must specify the authentication mechanisms you wish to use.
# This defaults to pam for PAM support, but may also include
# shadow or sasldb, like this:
# MECHANISMS=pam shadow
START=yes
PWDIR=/var/spool/postfix/var/run/saslauthd
PARAMS=-V -r -O localhost -m ${PWDIR}
PIDFILE=${PWDIR}/saslauthd.pid
MECHANISMS=rimap
-- /var/log/sasl.log --
saslauthd[22466] :main: num_procs : 5
saslauthd[22466] :main: mech_option: localhost
saslauthd[22466] :main: run_path :
/var/spool/postfix/var/run/saslauthd
saslauthd[22466] :main: auth_mech : rimap
saslauthd[22466] :ipc_init: using accept lock file:
/var/spool/postfix/var/run/saslauthd/mux.accept
--- 8 Snippit 2 8 ---
-- /etc/defaults/saslauthd --
# This needs to be uncommented before saslauthd will be run automatically
# START=yes
# You must specify the authentication mechanisms you wish to use.
# This defaults to pam for PAM support, but may also include
# shadow or sasldb, like this:
# MECHANISMS=pam shadow
START=yes
PWDIR=/var/spool/postfix/var/run/saslauthd
PARAMS=-V -r -O localhost -m ${PWDIR}
PIDFILE=${PWDIR}/saslauthd.pid
MECHANISMS=pam rimap
-- /var/log/sasl.log --
saslauthd[22578] :main: num_procs : 5
saslauthd[22578] :main: mech_option: localhost
saslauthd[22578] :main: run_path :
/var/spool/postfix/var/run/saslauthd
saslauthd[22578] :main: auth_mech : pam
saslauthd[22578] :ipc_init: using accept lock file:
/var/spool/postfix/var/run/saslauthd/mux.accept
** Affects: cyrus-sasl2 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
init.d script only seems to be seeing first auth_mech
https://launchpad.net/bugs/72097
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
